CVE-2026-106118

waiting for further signalsZero needs more public information before it can validate it.

GHSA-v76p-62qx-wwq2 ↗EUVD-2026-93770 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
SixLabors ImageSharp >= 3.0.0
fixed in 4.1.1
CWE-787 Out-of-bounds Write
ETK-2026-950, permanent identifier
pkg:nuget/ImageSharp
13d 13h 46msince last run
23mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+37h59m
0
+2h
+4h
+6h
+8h
+10h

description

ImageSharp versions before 4.1.1 can write outside a tile buffer while decoding tiled TIFF images using fax compression. An attacker who can supply such an image to an application may cause process termination and memory corruption; the application must decode attacker-controlled tiled, fax-compressed TIFF content.

mitigation

Upgrade ImageSharp to version 4.1.1 or later. Until upgraded, reject untrusted tiled TIFF files that use fax compression before decoding.

fixed in 4.1.1

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.60%48th percentile
agent run time
23m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-06 17:59Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-06 17:59Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-106118

{
  "etk_id": "ETK-2026-950",
  "cve_id": "CVE-2026-106118",
  "display_id": "CVE-2026-106118",
  "ghsa_id": "GHSA-v76p-62qx-wwq2",
  "euvd_id": "EUVD-2026-93770",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Out-of-bounds write in ImageSharp tiled TIFF decoding",
  "summary": "ImageSharp versions before 4.1.1 can write outside a tile buffer while decoding tiled TIFF images using fax compression. An attacker who can supply such an image to an application may cause process termination and memory corruption; the application must decode attacker-controlled tiled, fax-compressed TIFF content.",
  "mitigation": "Upgrade ImageSharp to version 4.1.1 or later. Until upgraded, reject untrusted tiled TIFF files that use fax compression before decoding.",
  "vendor": "SixLabors",
  "product": "ImageSharp",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 3.0.0"
      ],
      "ecosystem": "nuget",
      "fixed_versions": [
        "4.1.1"
      ],
      "package_name": "ImageSharp",
      "purl": "pkg:nuget/ImageSharp"
    }
  ],
  "cwes": [
    787
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": 0.006,
  "epss_percentile": 0.4812,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 23.059802883333333,
  "t0_at": "2026-10-06T17:59:02.778000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-06T17:59:02.778000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T17:59:02.778000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-106118"
    }
  }
}

published 2026-10-08 07:34Z
last change 2026-10-21 20:50Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.