CVE-2026-102505

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

GHSA-4rx6-cgv3-fmxp ↗EUVD-2026-90812 ↗

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.
cpan:Imager 1.036
fixed in 1.037
CWE-131 Incorrect Calculation of Buffer Size
ETK-2026-568, permanent identifier
16d 12h 28msince last run
47mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+75h30m
0
+2h
+4h
+6h
+8h
+10h

description

Imager versions before 1.037 can overflow a heap buffer when getsamples() retrieves float samples from a paletted image for multiple channels. An attacker may control bytes written beyond the buffer if the application processes an attacker-supplied paletted image under those conditions.

mitigation

Upgrade Imager to version 1.037 or later. Until upgraded, convert paletted images to a direct-colour format before requesting float samples from multiple channels.

fixed in 1.037

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.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.25%14th percentile
agent run time
47m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-01 13:11Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-10-01 13:11Z
  2. 2026-10-01 13:11Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-568",
  "cve_id": "CVE-2026-102505",
  "display_id": "CVE-2026-102505",
  "ghsa_id": "GHSA-4rx6-cgv3-fmxp",
  "euvd_id": "EUVD-2026-90812",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Heap buffer overflow in Imager getsamples()",
  "summary": "Imager versions before 1.037 can overflow a heap buffer when getsamples() retrieves float samples from a paletted image for multiple channels. An attacker may control bytes written beyond the buffer if the application processes an attacker-supplied paletted image under those conditions.",
  "mitigation": "Upgrade Imager to version 1.037 or later. Until upgraded, convert paletted images to a direct-colour format before requesting float samples from multiple channels.",
  "vendor": "cpan",
  "product": "cpan:Imager",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.036"
      ],
      "ecosystem": "cpan",
      "fixed_versions": [
        "1.037"
      ],
      "package_name": "Imager",
      "purl": null
    }
  ],
  "cwes": [
    131
  ],
  "cvss_score": 6.3,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L",
  "epss_score": 0.0025,
  "epss_percentile": 0.1499,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 47.397422283333334,
  "t0_at": "2026-10-01T13:11:51.967000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-01T13:11:51.967000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T13:11:51.967000+00:00",
      "url": "https://github.com/tonycoz/imager/security/advisories/GHSA-4rx6-cgv3-fmxp"
    }
  }
}

published 2026-10-04 15:54Z
last change 2026-10-21 05:00Z

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.