CVE-2026-129448

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

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

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-11-20), indicating real-world exploitation has been confirmed by US federal agencies. A secondary CVSS source baseline 9.8 retained for reference (NVD's own analysis pending). Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — KEV-added in the last 14 daysExploited in the wild

Also known asEUVD-2026-126955 (ENISA EUVD) · GHSA-pxp4-phq9-fx2q (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
CISA-KEV: ExploitedEPSS PROB: 5.5%CVSS: 9.8Exploit: Public PoCExposed services: Not assessed

The CVE record names the fixed release — apply it.

Deserialization of Untrusted Data in Apache Roller versions 4.0.0 through 6.1.4 allows an unauthenticated remote attacker to execute arbitrary code. The XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester.

This is the same vulnerability as CVE-2026-82384, which listed only Apache Roller 6.1.5 as affected. This issue is being actively exploited.

Users are recommended to upgrade to Apache Roller 6.1.6 or later, which disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled.

Users who cannot upgrade right away should set "enabledForExtensions" to "false" in WEB-INF/web.xml, or remove the "/roller-services/xmlrpc" servlet mapping, and restart Roller. Disabling XML-RPC in the administration UI is not enough, because older versions deserialize the request before checking that setting.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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: The CVE record names the fixed release. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.
EPSS PROB
5.5%
EPSS %ILE
92nd
KEV
⚠ Exploited

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

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

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
5.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Act at medium mission impactAttend at low mission impact; Act at medium or high.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.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)Attend at low mission impact; Act at medium or high.

The CVE record names the fixed release. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

CISA required action“Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://lists.apache.org/thread/cc0jck13nb9vvcmzxzwotr6n16mx28z9 · https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk · https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk · https://nvd.nist.gov/vuln/detail/CVE-2026-129448

Published

November 17, 2026

Last Modified

November 21, 2026

Advisory Details (5)

Auto-updated Nov 21, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Fix named in the CVE record. Sources: cisa, github_pr.
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-129448
GitHub pull request

Disable vendor extension types on the XML-RPC servlet

Fix merged in apache/roller PR #171 on 2026-09-05 — awaiting tagged release

https://github.com/apache/roller/pull/171

Vendor Advisories for CVE-2026-129448(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 23× 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 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-22 05:03 UTCEchelonGraph re-scored
  2. 2026-11-22 05:03 UTCGHSA enrichmentGHSA-pxp4-phq9-fx2q · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-21 16:38 UTCEPSS rescoreEPSS 5.5% · 92nd percentile
  4. 2026-11-21 05:28 UTCEchelonGraph re-scored
  5. 2026-11-21 05:28 UTCGHSA enrichmentGHSA-pxp4-phq9-fx2q · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-11-21 05:02 UTCEchelonGraph re-scored
  7. 2026-11-21 05:02 UTCGHSA enrichmentGHSA-pxp4-phq9-fx2q · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-11-20 21:07 UTCEchelonGraph re-scored
  9. 2026-11-20 21:07 UTCGHSA enrichmentGHSA-pxp4-phq9-fx2q · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-11-20 20:28 UTCGHSA enrichmentGHSA-pxp4-phq9-fx2q · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-11-20 19:28 UTCGHSA enrichmentGHSA-pxp4-phq9-fx2q · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-11-20 18:42 UTCEchelonGraph re-scored
  13. 2026-11-20 18:42 UTCGHSA enrichmentGHSA-pxp4-phq9-fx2q · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-11-20 18:37 UTCGHSA enrichmentGHSA-pxp4-phq9-fx2q · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-11-20 18:36 UTCEchelonGraph re-scored
  16. 2026-11-20 18:36 UTCCISA KEV update
  17. 2026-11-20 17:49 UTCGHSA enrichmentGHSA-pxp4-phq9-fx2q · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-11-20 16:44 UTCEchelonGraph re-scored
  19. 2026-11-20 16:44 UTCGHSA enrichmentGHSA-pxp4-phq9-fx2q · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-11-20 16:36 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  21. 2026-11-20 16:27 UTCGHSA enrichmentGHSA-pxp4-phq9-fx2q · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-11-20 05:01 UTCEchelonGraph re-scored
  23. 2026-11-20 05:01 UTCGHSA enrichmentGHSA-pxp4-phq9-fx2q · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-11-19 16:33 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  25. 2026-11-19 05:28 UTCEchelonGraph re-scored
Show 11 more
  1. 2026-11-19 05:28 UTCGHSA enrichmentGHSA-pxp4-phq9-fx2q · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-11-19 05:04 UTCEchelonGraph re-scored
  3. 2026-11-19 05:03 UTCGHSA enrichmentGHSA-pxp4-phq9-fx2q · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-18 16:34 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  5. 2026-11-18 12:19 UTCGHSA enrichmentGHSA-pxp4-phq9-fx2q · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-11-17 12:46 UTCEchelonGraph re-scored
  7. 2026-11-17 12:46 UTCGHSA enrichmentGHSA-pxp4-phq9-fx2q · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-11-17 12:03 UTCENISA EUVD ID recordedEUVD-2026-126955 · Source: ENISA EUVD
  9. 2026-11-17 11:28 UTCEchelonGraph re-scored
  10. 2026-11-17 11:09 UTCEchelonGraph re-scoredFirst assessed: 9.8 CRITICAL
  11. 2026-11-17 11:08 UTCMITRE cvelistV5first tracked

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCYanixos/APACHE-CVE-2026-129448
    Published Nov 18, 2026

    CVE-2026-129448 Apache Roller XML-RPC deserialization : PoC, scanner, exploit, lab

    Open source ↗

Frequently asked(6)

What is CVE-2026-129448?
CVE-2026-129448 is a critical-severity vulnerability; its CVE record was published on November 17, 2026. Deserialization of Untrusted Data in Apache Roller versions 4.0.0 through 6.1.4 allows an unauthenticated remote attacker to execute arbitrary code. The XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester. This is the same vulnerability as…
When was the CVE record for CVE-2026-129448 published?
The CVE record for CVE-2026-129448 was published on November 17, 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 21, 2026; the record at its source may have been updated since.
Is CVE-2026-129448 actively exploited?
Yes. CISA added CVE-2026-129448 to the Known Exploited Vulnerabilities catalog on November 20, 2026, affecting Apache Roller. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. The CVE record names the fixed release. Apply it.
What is the CVSS score of CVE-2026-129448?
CVE-2026-129448 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
Which products are affected by CVE-2026-129448?
CVE-2026-129448 affects Apache Roller.
How do I remediate CVE-2026-129448?
The CVE record for CVE-2026-129448 names the fix: "Users are recommended to upgrade to Apache Roller 6.1.6 or later, which disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled." The vendor advisories EchelonGraph has for CVE-2026-129448 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-129448?

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