Quick answers
- Is CVE-2026-123374 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123374 being exploited in the wild.
- How severe is CVE-2026-123374?
- Informational severity, published 11 November 2026.
- Which products and versions are affected?
- Apache Roller 4.0 through 6.1.6.
- Is there a fix for CVE-2026-123374?
- Yes: fixed in 6.1.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123374 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-123374?
- Check whether you run Apache Roller at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 6.1.7
Technical details
The vulnerability exists in the XML-RPC client library's deserialization of untrusted Java object data returned in weblog update ping responses. When Roller sends a ping to a remote URL, it deserializes the XML-RPC response without proper validation, enabling an attacker controlling that response to inject malicious serialized objects that execute code in the Roller server process. The fix in version 6.1.7 removes the unsafe deserialization by replacing the XML-RPC client library with a custom, hardened implementation that only parses specific fields without deserializing arbitrary objects.
Affected products
- Apache Roller 4.0 through 6.1.6
Timeline
- 2026-11-11: disclosed
- 2026-11-07: patched