CVE-2026-123374 · Runtime
NO FIX YET · SEE WHAT TO DO
Apache Roller deserializes Java object data from the response of a weblog update ping target, so whoever controls that response can run code in the Roller server process. Affected versions are 4.0 through 6.1.6.
first public Nov 11, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Any Apache Roller server from 4.0 through 6.1.6 that sends weblog update pings is exposed, since the flaw is in handling the response from the ping target. The sources do not say whether pings must be enabled by a non-default setting. Teams running Roller 6.1.7 or later, or not running Roller, can skip it.
Not affected if version-6.1.7-or-later
Who cares apache-roller, java, self-hosted
4.0 through 6.1.6 are affected.6.1.7, which removes the unsafe deserialization.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.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.