CVE-2026-85644

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-28. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this week
7.5EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

XS::Parse::Infix versions from 0.40 through 0.49 for Perl treat a number as an array reference.

The wrapper function XS::Parse::Infix generates for a list-associative infix operator checks whether arguments are array references, but it tests using SvRV() rather than SvROK(). SvRV() reads a union slot that only holds a referent once SvROK(sv) is true, so the guard never validates that it is a reference. For an IV or NV that slot holds the number itself, SvRV() returns the caller's value and SvTYPE() dereferences it at offset 12. This will generally result in a segmentation fault.

An application that hands the wrapper a list built from decoded input (for example, from JSON) lets whoever supplies a number in that list choose the address that the interpreter dereferences.

An ordinary string's byte 12 is rarely SVt_PVAV so the guard croaks by luck, but an attacker-crafted string carrying 0x0b there passes, and the buffer is then used as an AV head, with AvARRAY taken from bytes 16-23 and its entries pushed onto the Perl stack as live SVs.

A simple proof-of-concept uses the zip operator:

use Syntax::Operator::Zip 'zip';

my @args = ([1], 2); zip(@args);

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
49
EG Risk 49/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 28, 2026

Last Modified

September 30, 2026

Advisory Details (3)

Auto-updated Sep 30, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

oss-security - CVE-2026-85644: XS::Parse::Infix versions from 0.40 through 0.49 for Perl treat a number as an array reference

http://www.openwall.com/lists/oss-security/2026/09/28/14

Vendor Advisories for CVE-2026-85644(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 28× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 06:37 UTCGHSA enrichment
  2. 2026-10-03 18:52 UTCEG score recompute
  3. 2026-10-03 18:52 UTCGHSA enrichment
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-03 07:08 UTCGHSA enrichment
  6. 2026-10-02 19:23 UTCEG score recompute
  7. 2026-10-02 19:23 UTCGHSA enrichment
  8. 2026-10-02 17:57 UTCEPSS rescore
  9. 2026-10-02 07:38 UTCGHSA enrichment
  10. 2026-10-01 19:53 UTCEG score recompute
  11. 2026-10-01 19:53 UTCGHSA enrichment
  12. 2026-10-01 19:50 UTCEPSS rescore
  13. 2026-10-01 08:08 UTCEG score recompute
  14. 2026-10-01 08:08 UTCGHSA enrichment
  15. 2026-09-30 20:23 UTCGHSA enrichment
  16. 2026-09-30 19:56 UTCEG score recompute▲ 7.50
  17. 2026-09-30 19:56 UTCGHSA enrichment
  18. 2026-09-30 19:55 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  19. 2026-09-30 15:04 UTCEPSS rescore
  20. 2026-09-29 19:07 UTCEG score recompute
  21. 2026-09-29 19:07 UTCGHSA enrichment
  22. 2026-09-28 19:29 UTCGHSA enrichment
  23. 2026-09-28 19:21 UTCNVD update
  24. 2026-09-28 18:37 UTCGHSA enrichment
  25. 2026-09-28 18:36 UTCMITRE cvelistV5
Show 3 more
  1. 2026-09-28 17:33 UTCNVD update
  2. 2026-09-28 16:33 UTCEG score recompute
  3. 2026-09-28 16:31 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-85644?
CVE-2026-85644 is a high vulnerability published on September 28, 2026. XS::Parse::Infix versions from 0.40 through 0.49 for Perl treat a number as an array reference. The wrapper function XS::Parse::Infix generates for a list-associative infix operator checks whether arguments are array references, but it tests using SvRV() rather than SvROK(). SvRV() reads a union…
When was CVE-2026-85644 disclosed?
CVE-2026-85644 was first published on September 28, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-85644 actively exploited?
CVE-2026-85644 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-85644?
CVE-2026-85644 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-85644?
No fix for CVE-2026-85644 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-85644 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-85644

Explore →

Is Your Infrastructure Affected by CVE-2026-85644?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.