CVE-2026-105152 · Package
NO FIX YET · SEE WHAT TO DO
Apache Roller 4.0 through 6.1.6 lets a weblog administrator author a template that exposes the underlying persistent objects behind weblog and entry data. An attacker can read the stored password hash of the weblog's creator and of authors whose entries render on the page.
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 installation from 4.0 through 6.1.6 where a weblog administrator can author templates is exposed. The sources do not say whether managed or hosted Roller deployments are handled differently. Instances where only trusted operators can edit templates carry less risk.
Not affected if no-template-authors, roller-6.1.7-or-later
Who cares apache-roller, java, self-hosted
4.0 through 6.1.6 are affected.6.1.7 or later.Exposure of Sensitive Information to an Unauthorized Actor in Apache Roller 4.0 through 6.1.6 allows a weblog administrator to read another user's stored password hash by authoring a custom weblog template that reaches the wrapped persistent object behind the template's weblog or entry data, rather than the reduced set of fields the wrapper is meant to expose. Roller treats weblog administrators as untrusted and exposes weblog and entry data to templates only through wrapper classes, but a public accessor on those wrapper classes returned the underlying persistent object directly, including the stored password hash of the weblog's creator and of any author whose entry renders on the page. No non-default configuration is required; this affects any weblog whose administrator can author templates. Users are recommended to upgrade to Apache Roller 6.1.7 or later, which removes template access to the underlying wrapped objects.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
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.