shiro-web (Jakarta Pages) · shiro:principal tags
Source GCVE Database
Not known to be exploited · CVSS 2.1 Low : upgrade to 3.0.2 when convenient.
Data as of 16 Nov 2026, 17:21 UTC
Thin evidence
One scorer or none| CNA (apache) | CVSS 4.0 | 2.1 |
|---|
- Patch
- Available – fixed in 3.0.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/S:N/AU:N/V:D/RE:L/U:GreenExploitation evidence
Disclosed: evidence found.
CVE published 16 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 15 Nov 2026.
What to do
Upgrade Apache Shiro and org.apache.shiro/shiro-web and org.apache.shiro/shiro-jakarta-ee to 3.0.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Shiroorg.apache.shiro:shiro-web | Affected
| Fixed in
|
| Apache Shiroorg.apache.shiro:shiro-jakarta-ee | Affected
| Fixed in
|
Mavenorg.apache.shiro/shiro-webpkg:maven/org.apache.shiro/shiro-webOther threats | Affected
| Fixed in
|
Mavenorg.apache.shiro/shiro-jakarta-eepkg:maven/org.apache.shiro/shiro-jakarta-eeOther 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
Upgrade Apache Shiro to version 3.0.2 or later, where the output escaping is implemented. Alternatively, ensure that principal values are validated on input to prevent injection of malicious scripts.
Description
Apache Shiro versions through 3.0.1 contain a cross-site scripting (XSS) vulnerability in the shiro:principal tags used in shiro-web (Jakarta Pages) and shiro-jakarta-ee (Jakarta Faces). The tags did not escape their output, which could allow XSS if the principal value is not fully trusted. This vulnerability is addressed in version 3.0.2 and later by escaping the output. Alternatively, validating principal values on input can mitigate the risk.