CVE-2026-111234

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 5.9 from GitHub Security Advisory (severity: HIGH) published 2026-10-15. A secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-102346 (ENISA EUVD) · GHSA-9fwh-fc64-58p8 (GitHub Security Advisories)Source: ENISA EUVD

5.9EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.9Exploit: No code on recordExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

SimplePie through 1.9.0 contains a local file read vulnerability that allows malicious feed servers to read server files by supplying file:// URLs in redirects or autodiscovery links. Attackers can return a Location header or feed link pointing to a file:// path, causing file_get_contents() to read files accessible to the web server process.

CVSS v3
5.9
EG Score
5.9MEDIUMhigh confidence
EG Risk
43
EG Risk 43/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity59% × 45%
Impact severity (EG Severity): CVSS 5.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.

EG Severity
5.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 15, 2026

Last Modified

October 16, 2026

Advisory Details (8)

Auto-updated Oct 15, 2026
Fix referenced — no release confirmed yet. Sources: github_pr.
Web page

SimplePie through 1.9.0 Local File Read via file:// Redirect | Advisories | VulnCheck

https://www.vulncheck.com/advisories/simplepie-through-1.9.0-local-file-read-via-file-redirect
GitHub pull request

Implement safe-by-default URL policy

Upstream fix in progress (PR #991 · simplepie/simplepie, state=open)

https://github.com/simplepie/simplepie/pull/991
Web page

Should we filter for SSRF by default? · Issue #968 · simplepie/simplepie · GitHub

https://github.com/simplepie/simplepie/issues/968
Web page

simplepie/src/HTTP/Psr18Client.php at 76cccb1b2c5dcaf44f304c925ab30c0f48643992 · simplepie/simplepie · GitHub

https://github.com/simplepie/simplepie/blob/76cccb1b2c5dcaf44f304c925ab30c0f48643992/src/HTTP/Psr18Client.php#L75-L157
Web page

simplepie/src/File.php at 76cccb1b2c5dcaf44f304c925ab30c0f48643992 · simplepie/simplepie · GitHub

https://github.com/simplepie/simplepie/blob/76cccb1b2c5dcaf44f304c925ab30c0f48643992/src/File.php#L289-L293
Web page

simplepie/src/File.php at 76cccb1b2c5dcaf44f304c925ab30c0f48643992 · simplepie/simplepie · GitHub

https://github.com/simplepie/simplepie/blob/76cccb1b2c5dcaf44f304c925ab30c0f48643992/src/File.php#L160-L176
Web page

GitHub - simplepie/simplepie: A simple Atom/RSS parsing library for PHP. · GitHub

https://github.com/simplepie/simplepie
Web page

GitHub - abraxas/pfsense-rss-file-redirect: pfSense CE 2.9.0-DEVELOPMENT - Medium - Remote - File read - RSS file:// redirect · GitHub

https://github.com/abraxas/pfsense-rss-file-redirect

Vendor Advisories for CVE-2026-111234(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 23× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  3. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  4. 2026-10-25 14:52 UTCEG score recompute
  5. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  6. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  7. 2026-10-23 07:58 UTCEG score recompute
  8. 2026-10-23 07:58 UTCGHSA enrichmentGHSA-9fwh-fc64-58p8 · GitHub severity HIGH · GitHub CVSS 5.9
  9. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  10. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  11. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  12. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  14. 2026-10-18 05:05 UTCEG score recompute
  15. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-10-16 18:32 UTCEG score recompute
  17. 2026-10-16 18:32 UTCGHSA enrichmentGHSA-9fwh-fc64-58p8 · GitHub severity HIGH · GitHub CVSS 5.9
  18. 2026-10-16 17:31 UTCEG score recompute
  19. 2026-10-16 17:31 UTCGHSA enrichmentGHSA-9fwh-fc64-58p8 · GitHub severity HIGH · GitHub CVSS 5.9
  20. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  21. 2026-10-15 19:37 UTCEG score recompute
  22. 2026-10-15 19:01 UTCEG score recomputeFirst assessed: 5.9 MEDIUM
  23. 2026-10-15 18:57 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-111234?
CVE-2026-111234 is a medium-severity vulnerability; its CVE record was published on October 15, 2026. SimplePie through 1.9.0 contains a local file read vulnerability that allows malicious feed servers to read server files by supplying file:// URLs in redirects or autodiscovery links. Attackers can return a Location header or feed link pointing to a file:// path, causing filegetcontents() to read…
When was CVE-2026-111234 made public?
CVE-2026-111234 was made public on September 23, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 15, 2026. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-111234 actively exploited?
CVE-2026-111234 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-111234?
CVE-2026-111234 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-111234?
A fix for CVE-2026-111234 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-111234 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-111234?

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