APACHE ROLLER · CVE-2026-108338 · Package
NO FIX YET · SEE WHAT TO DO
Apache Roller 5.0.1 through 6.1.6 lets an authenticated Author store script in weblog entry tags submitted through AtomPub. The script runs in the browser of anyone who views the weblog.
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.
Sites running Apache Roller 5.0.1 through 6.1.6 with AtomPub enabled, where weblog authors are not fully trusted. Installations with AtomPub disabled (the default) or with trusted authors are less exposed. The bundled gaurav, fauxcoly and frontpage themes and the showEntryTags macro are the output points that print unescaped tag names.
Not affected if atompub-disabled, default-config, trusted-authors
Who cares apache-roller, atompub, java, self-hosted
5.0.1 through 6.1.6.weblogAdminsUntrusted is set to true (default since 6.1.4).6.1.7 or later, which removes HTML characters from tag names, including names stored earlier.Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in Apache Roller 5.0.1 through 6.1.6 allows an authenticated user with the Author role on a weblog to store script in entry tags submitted through AtomPub. Roller's tag filter allowed HTML characters in tag names, and the bundled gaurav, fauxcoly and frontpage themes and the showEntryTags macro print tag names without escaping, so the script runs in the browser of anyone who views the weblog. This matters when weblog authors are not trusted with script (weblogAdminsUntrusted=true, the default since 6.1.4). AtomPub is disabled by default. Users are recommended to upgrade to Apache Roller 6.1.7 or later, which removes HTML characters from tag names, including names stored earlier.
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.