Apache Roller remote code execution in XML-RPC ping client
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Summary
Apache Roller has a flaw where its XML-RPC client, when sending a weblog update ping, unsafely deserializes Java object data in the ping target's response. An attacker who controls that response can run code on the Roller server.
Written by a model
Original description
Deserialization of Untrusted Data vulnerability in Apache Roller. When Roller sends a weblog update ping, its XML-RPC client deserializes Java object data contained in the ping target's response, so a party that controls that response can run code in the Roller server process. This issue affects Apache Roller from 4.0 through 6.1.6. Users are recommended to upgrade to version 6.1.7, which removes the unsafe deserialization.
What to do
Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-123374 (Apache Roller: Deserialization of untrusted data in weblog update ping responses), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-123374 (entry last updated 2026-11-17):
Affected:
- Apache Software Foundation Apache Roller: from 4.0, through 6.1.6
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-123374 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-123374 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread/577orljt8673gcvcv6nvwo2tnvykyxmt
- https://github.com/apache/roller/pull/236
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-123374
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-123374"}.Affected versions
- Apache Software Foundation Apache RollerFrom 4.0 · through 6.1.6
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.8/10CVSS 9.8
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now6 days
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
- Posted on X by cve.now
Public exploit activity
- EPSS: 0.56%
- Posted on X by cve.now Nov 17
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | lists.apache.org · thread/577orljt8673gcvcv6nvwo2tnvykyxmt |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-123374 |
| Record | NVD · CVE-2026-123374 |
| Other links 1 | |
| Patch | GitHub · apache/roller · Pull request #236 |
Questions about CVE-2026-123374
Is CVE-2026-123374 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-123374?
Apache Roller: from 4.0 through 6.1.6.
Source: cve.now feed data
Related
- CVE-2026-129448Apache Roller: Unauthenticated deserialization in the XML-RPC endpoint (releases before 6.1.5)
- CVE-2026-122300Apache Roller: Limited weblog members can remove or change published entries
- CVE-2026-118411Apache Roller: Cross-site request forgery through GET requests to administrative actions
- CVE-2026-82380Apache Roller: CSRF protection bypass via self-generated salt validation
- CVE-2026-105153Apache Roller: XML external entity processing in AtomPub entry parsing
- CVE-2026-82379Apache Roller: WSSE digest authentication headers can be replayed
No corrections so far. Something wrong on this page? Report an error.