Skip to content

ApplicationsCritical 9.8In CISA KEVPatch available

CVE-2026-129448

Unauthenticated RCE via Apache Roller XML-RPC deserialization

How scary is it?

updated 21 Nov 2026
  • Yes

    Works without logging in1

    No account and no user action needed (CVSS PR:N, UI:N).

  • Yes

    Reachable over the network1

    Can be attacked remotely (CVSS AV:N).

  • Yes

    Proof-of-concept code is public2

    3 GitHub proofs of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.

  • Yes

    Attacks seen in the wild3

    CISA lists it as exploited in the wild.

  • Yes

    On CISA's exploited list (since 20 Nov 2026)3

    CISA deadline for US federal agencies: 23 Nov 2026.

Scare-o-meter

Drop everything

Attackers are already on it. Patch now.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: Listed in CISA's Known Exploited Vulnerabilities catalog: it is being used in attacks.3 Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run Apache Software Foundation Apache Roller in an affected version>= 4.0.0 and < 6.1.5

    The CVE record states no fixed release.

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. An attacker can reach it over the network

    CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per our analysisA patch is available

    The CVE record we hold states no fixed release number. See the advisories in the references.

    See the references

  2. CISA required actionApply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing…

    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.

    CISA's required action for this KEV entry, due 23 Nov 2026 for US federal agencies.

    Source 3

  3. Recommendation, AI-writtenUpgrade to Roller 6.1.6+ or disable XML-RPC / set enabledForExtensions=false and remove servlet mapping

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

Major vulnerability. Listed in CISA's Known Exploited Vulnerabilities catalog: it is being used in attacks.

CVSS
9.8Criticalscored by the publisher (CNA)
Exploited in the wild
Yes, in CISA KEV since 20 Nov 2026CISA deadline for US federal agencies: 23 Nov 2026unvetted proof-of-concept code on github
EPSS
5.5%chance of exploitation in the next 30 daystop 8% of scored CVEsFIRST score of 21 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
17 Nov 2026analysed here 21 Nov 2026

Do first. 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. (CISA's required action for this KEV entry)

Summary

Impact

Unauthenticated remote code execution via XML-RPC deserialization; attackers can achieve full server compromise, data theft, or deploy ransomware.

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
Partly. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Apache Software Foundation Apache Roller>= 4.0.0 and < 6.1.5Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • Apache Roller 4.0.0 - 6.1.4
  • XML-RPC endpoint /roller-services/xmlrpc

Fix and mitigation

Action required

Immediate action required

WAF and other mitigations

Can a WAF block it? Partly. The attack is delivered via HTTP requests to a specific XML-RPC endpoint, which is unusual and can be detected by matching requests to that endpoint containing XML-RPC payloads. A WAF rule can match XML-RPC requests to /roller-services/xmlrpc endpoint. No tracked WAF vendor has published a rule for this CVE yet, so you would write it yourself.

What a custom rule would match: XML-RPC requests to /roller-services/xmlrpc endpoint

Also consider: patch · custom WAF rule · allow-list classes

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 20 Nov 2026.
CISA due date
23 Nov 2026, the remediation deadline for US federal agencies
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.
Public exploit code
Unvetted proof-of-concept code on GitHub: 3 GitHub proofs of concept
CISA SSVC
exploitation active, automatable yes, technical impact totalAssessed by CISA 18 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 17 Nov 2026Published
  2. 18 Nov 2026First proof-of-concept repository on GitHub (unvetted)1 day later
  3. 18 Nov 2026CISA SSVC assessment: exploitation activesame day later
  4. 20 Nov 2026Added to CISA KEV (exploited in the wild)2 days later
  5. 21 Nov 2026CVE record last updated1 day later
  6. 21 Nov 2026Analysed by vulneraibility.comsame day later
  7. 23 Nov 2026CISA remediation due date (US federal agencies)2 days later

Common questions

Is CVE-2026-129448 being exploited?

Yes. CVE-2026-129448 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2026-129448?

CVE-2026-129448 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-129448?

Yes. A fix has been recorded for CVE-2026-129448. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-129448 affect?

CVE-2026-129448 affects Apache Roller 4.0.0 - 6.1.4, XML-RPC endpoint /roller-services/xmlrpc. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-129448?

Upgrade to Roller 6.1.6+ or disable XML-RPC / set enabledForExtensions=false and remove servlet mapping

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

5 references in the CVE record, grouped by the tags the record gives them.

Advisories (2)

Patches (1)

Other links (2)

  • cve.org /CVERecord?id=CVE-2026-82384
  • cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-129448

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.