CVE-2026-132252

MEDIUMPre-NVD 4.14.1
EchelonGraph scoreHIGH confidence

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

Score 4.1 from GitHub Security Advisory (severity: LOW) published 2026-11-19. A secondary CVSS source baseline 4.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-129318 (ENISA EUVD) · GHSA-fjr6-gprv-v9w6 (GitHub Security Advisories)Source: ENISA EUVD

4.1EG
EchelonGraph verdictMonitorThe upstream fix is not in a release yet: until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.1Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

A vulnerability was found in October CMS up to 4.4.6. This affects the function validateExternalImageHost of the file modules/system/classes/resizeimages/ValidatesExternalImages.php of the component Image Resizer. Performing a manipulation of the argument url results in server-side request forgery. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitability is reported as difficult. The exploit has been made public and could be used. Upgrading to version 4.4.7 mitigates this issue. The patch is named f6372867006c03141944e7b57396a726eb02acf0. You should upgrade the affected component.

CVSS v3
4.1
EG Score
4.1MEDIUMhigh confidence
EG Risk
19
EG Risk 19/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)
Severity41% × 45%
Impact severity (EG Severity): CVSS 4.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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: An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it.
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 (4.1): severity, escalated by confirmed exploitation. This CVE's 4.1 is its impact severity (EG Severity), not escalated.

EG Severity
4.1 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. 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it.

Exploitation none (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.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: 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

November 18, 2026

Last Modified

November 19, 2026

Advisory Details (1)

Auto-updated Nov 18, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
GitHub commit

commit f6372867006c (octobercms/october)

Fix landed in octobercms/october commit f6372867006c — awaiting tagged release

https://github.com/octobercms/october/commit/f6372867006c03141944e7b57396a726eb02acf0

Vendor Advisories for CVE-2026-132252(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 12× in last 7d / 12× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  3. 2026-11-20 05:48 UTCEchelonGraph re-scored
  4. 2026-11-20 05:48 UTCGHSA enrichmentGHSA-fjr6-gprv-v9w6 · GitHub severity LOW · GitHub CVSS 4.1
  5. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-11-19 16:32 UTCEchelonGraph re-scored
  7. 2026-11-19 16:32 UTCGHSA enrichmentGHSA-fjr6-gprv-v9w6 · GitHub severity LOW · GitHub CVSS 4.1
  8. 2026-11-19 16:27 UTCNVD updateCVSS v4 → 1.2
  9. 2026-11-19 16:19 UTCEchelonGraph re-scored
  10. 2026-11-19 16:18 UTCGHSA enrichmentGHSA-fjr6-gprv-v9w6 · GitHub severity LOW · GitHub CVSS 4.1
  11. 2026-11-19 16:03 UTCMITRE cvelistV5CVSS v4 → 2.1
  12. 2026-11-19 00:46 UTCEchelonGraph re-scored
  13. 2026-11-19 00:46 UTCGHSA enrichmentGHSA-fjr6-gprv-v9w6 · GitHub severity LOW · GitHub CVSS 4.1
  14. 2026-11-18 23:03 UTCENISA EUVD ID recordedEUVD-2026-129318 · Source: ENISA EUVD
  15. 2026-11-18 22:28 UTCEchelonGraph re-scored
  16. 2026-11-18 22:27 UTCNVD updateCVSS v4 → 1.2
  17. 2026-11-18 22:04 UTCEchelonGraph re-scoredFirst assessed: 4.1 MEDIUM
  18. 2026-11-18 22:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-132252?
CVE-2026-132252 is a medium-severity vulnerability; its CVE record was published on November 18, 2026. A vulnerability was found in October CMS up to 4.4.6. This affects the function validateExternalImageHost of the file modules/system/classes/resizeimages/ValidatesExternalImages.php of the component Image Resizer. Performing a manipulation of the argument url results in server-side request forgery.…
When was the CVE record for CVE-2026-132252 published?
The CVE record for CVE-2026-132252 was published on November 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 19, 2026; the record at its source may have been updated since.
Is CVE-2026-132252 actively exploited?
CVE-2026-132252 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-132252?
CVE-2026-132252 has a CVSS base score of 4.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-132252?
An upstream fix for CVE-2026-132252 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-132252 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-132252?

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