CVE-2026-123374: Apache Roller · Deserialization of Untrusted Data
Affects Apache RollerSource CVE Database V5
Not known to be exploited · fixed in 6.1.7 : patch Apache Roller soon.
Data as of 11 Nov 2026, 13:03 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 6.1.7
Exploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache Roller | Affected
| Fixed in– |
GitHubApache Rollerpkg:github/Apache RollerOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade Apache Roller to version 6.1.7 or later, which removes the unsafe deserialization and mitigates the vulnerability. No other mitigation is indicated or recommended by the vendor.
Description
Apache Roller versions 4.0 through 6.1.6 are affected by a deserialization of untrusted data vulnerability (CWE-502). This occurs when the XML-RPC client in Roller deserializes Java object data from a weblog update ping response, allowing an attacker controlling that response to execute code within the Roller server process. The issue is resolved in version 6.1.7, which removes the unsafe deserialization.