{"schema":"vulnpedia.research/1","cve":"CVE-2026-74763","references":[{"url":"http://www.openwall.com/lists/oss-security/2026/11/14/4","source":"mitre","sourceId":"CVE","modified":"2026-11-16T14:21:23.528Z","origins":[{"source":"mitre","sourceId":"CVE","modified":"2026-11-16T14:21:23.528Z","url":"http://www.openwall.com/lists/oss-security/2026/11/14/4"},{"source":"nvd","sourceId":"CVE-2026-74763","modified":"2026-11-16T21:17:30.917","url":"http://www.openwall.com/lists/oss-security/2026/11/14/4"}],"tags":[]},{"url":"https://lists.apache.org/thread/gfy3dyh5vfocp34l0bc6dy8gbbjgs3pf","tags":["vendor-advisory"],"source":"mitre","sourceId":"apache","modified":"2026-11-16T13:29:15.251Z","origins":[{"source":"mitre","sourceId":"apache","modified":"2026-11-16T13:29:15.251Z","tags":["vendor-advisory"],"url":"https://lists.apache.org/thread/gfy3dyh5vfocp34l0bc6dy8gbbjgs3pf"},{"source":"nvd","sourceId":"CVE-2026-74763","modified":"2026-11-16T21:17:30.917","url":"https://lists.apache.org/thread/gfy3dyh5vfocp34l0bc6dy8gbbjgs3pf"}]},{"source":"euvd","sourceId":"EUVD-2026-126383","url":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-126383","tags":["ADVISORY"],"origins":[{"source":"euvd","sourceId":"EUVD-2026-126383","tags":["ADVISORY"],"url":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-126383"}]}],"packages":[],"pocCandidates":[],"cataloguedPoc":[],"vendorStatements":[],"sourceTimes":{"cisa-kev":"2026-11-16T23:38:29.105Z","exploitdb":"2026-11-16T23:38:29.105Z","epss":"2026-11-16T23:38:29.105Z","nuclei":"2026-11-16T23:38:29.105Z","osv-PyPI":"2026-11-16T19:57:58.815Z","osv-npm":"2026-11-16T19:58:33.604Z","osv-Maven":"2026-11-16T19:58:01.751Z","osv-Go":"2026-11-16T19:58:04.353Z","osv-crates_io":"2026-11-16T19:58:05.248Z","osv-RubyGems":"2026-11-16T19:58:06.356Z","osv-Packagist":"2026-11-16T19:58:09.520Z","osv-NuGet":"2026-11-16T19:58:10.841Z","osv-Pub":"2026-11-16T19:58:11.100Z","osv-SwiftURL":"2026-11-16T19:58:11.345Z","osv-GitHub_Actions":"2026-11-16T19:58:11.655Z","osv-_EMPTY_":"2026-11-16T19:58:15.995Z","poc-in-github":"2026-11-16T19:58:22.103Z","metasploit":"2026-11-16T23:12:33.771Z","redhat-vex":"2026-11-16T20:10:49.226Z","euvd":"2026-11-16T19:57:45.452Z","vulncheck-kev":"2026-11-16T23:12:33.771Z","zdi":"2026-11-16T23:38:47.027Z","oss-security":"2026-11-16T23:38:47.027Z","full-disclosure":"2026-11-16T23:38:47.027Z","cert-cc":"2026-11-16T23:38:47.027Z","fkie-nvd-2026":"2026-11-16T22:37:41.646Z","fkie-nvd-2025":"2026-11-16T20:12:25.069Z","ghsa":"2026-11-16T23:13:14.565Z","pysec":"2026-11-16T23:13:14.565Z","go":"2026-11-16T23:13:14.565Z","rustsec":"2026-11-16T23:13:14.565Z","primary":"2026-11-16T20:38:00.479Z","nvd":"2026-11-16T21:17:30.917"},"sourceFields":{"schema":"vulnpedia.source-fields/1","primary":{"description":"Authorization annotations, such as @RequiresRoles and @RequiresPermissions, are not always enforced in some class or interface hierarchies.\nAnnotations declared on an interface were not enforced when using the shiro-guice, shiro-aspectj, shiro-cdi or shiro-jakarta-ee modules.\nIn addition, annotations declared on a class or a superclass were not always enforced when using shiro-guice or shiro-aspectj, allowing an unauthorized caller to invoke methods that should be protected.\nThis issue affects all Apache Shiro versions through 3.0.1, with impact depending on module and where annotations are declared.\n\nMitigation: Upgrade to version 3.0.2 or later, which fixes the issue. The annotation closest to the invoked method now takes precedence.\nAlternatively, declare authorization annotations directly on each protected implementing method.","published":"2026-11-16","cwe":[{"id":"CWE-862","name":"Missing Authorization"}],"labels":{"vendors":["Apache Software Foundation"],"products":["Apache Shiro"]},"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial"}},"nvd":{"description":"Authorization annotations, such as @RequiresRoles and @RequiresPermissions, are not always enforced in some class or interface hierarchies.\nAnnotations declared on an interface were not enforced when using the shiro-guice, shiro-aspectj, shiro-cdi or shiro-jakarta-ee modules.\nIn addition, annotations declared on a class or a superclass were not always enforced when using shiro-guice or shiro-aspectj, allowing an unauthorized caller to invoke methods that should be protected.\nThis issue affects all Apache Shiro versions through 3.0.1, with impact depending on module and where annotations are declared.\n\nMitigation: Upgrade to version 3.0.2 or later, which fixes the issue. The annotation closest to the invoked method now takes precedence.\nAlternatively, declare authorization annotations directly on each protected implementing method.","published":"2026-11-16","cwe":[{"id":"CWE-862","name":"Missing authorization"}],"labels":{"vendors":[],"products":[]},"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial"}}},"labels":{"vendors":["Apache Software Foundation"],"products":["Apache Shiro"]},"evidence":{"version":"2026-11-16T23:39:03.167Z#99afe796fab023feaaf636b0fead9b19b39569301d4849ccd71b45e5d24dd128","checkedAt":"2026-11-16T23:39:03.167Z","changedAt":"2026-11-16T23:27:28.275Z","pocChangedAt":null}}