{"schema":"vulnpedia.research/1","cve":"CVE-2026-88019","references":[{"url":"http://www.openwall.com/lists/oss-security/2026/11/14/3","source":"mitre","sourceId":"CVE","modified":"2026-11-16T14:21:30.923Z","origins":[{"source":"mitre","sourceId":"CVE","modified":"2026-11-16T14:21:30.923Z","url":"http://www.openwall.com/lists/oss-security/2026/11/14/3"},{"source":"nvd","sourceId":"CVE-2026-88019","modified":"2026-11-16T21:17:31.790","url":"http://www.openwall.com/lists/oss-security/2026/11/14/3"}],"tags":[]},{"url":"https://lists.apache.org/thread/fvlsfo9zoz5rqqn15pz4b72nkjbjmfw7","tags":["vendor-advisory"],"source":"mitre","sourceId":"apache","modified":"2026-11-16T13:25:06.046Z","origins":[{"source":"mitre","sourceId":"apache","modified":"2026-11-16T13:25:06.046Z","tags":["vendor-advisory"],"url":"https://lists.apache.org/thread/fvlsfo9zoz5rqqn15pz4b72nkjbjmfw7"},{"source":"nvd","sourceId":"CVE-2026-88019","modified":"2026-11-16T21:17:31.790","url":"https://lists.apache.org/thread/fvlsfo9zoz5rqqn15pz4b72nkjbjmfw7"}]},{"source":"euvd","sourceId":"EUVD-2026-126381","url":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-126381","tags":["ADVISORY"],"origins":[{"source":"euvd","sourceId":"EUVD-2026-126381","tags":["ADVISORY"],"url":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-126381"}]}],"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:29.272Z","nvd":"2026-11-16T21:17:31.790"},"sourceFields":{"schema":"vulnpedia.source-fields/1","primary":{"description":"When Apache Shiro is used with the Jakarta EE integration module, the automatic form saving feature weakens the security of a form that is resubmitted after login.\nCookies set by the application during the resubmission could lose their security attributes, such as `Secure` and `SameSite`.\nIn addition, the resubmitted form data and cookies could be sent to an untrusted host.\nThis issue affects Apache Shiro from 2.0.0-alpha through 3.0.1, only when using `shiro-jakarta-ee` integration module with form saving enabled (the default).\n\nMitigation: Upgrade to version 3.0.2 or later, which no longer replays the form over the network, and avoids this class of issues entirely.\nAlternatively, you can set the `org.apache.shiro.form-resubmit-host` (String) and `org.apache.shiro.form-resubmit-port` (Integer) system properties to restrict the host and port that Shiro will connect to when resubmitting a form.","published":"2026-11-16","cwe":[{"id":"CWE-918","name":"Server-Side Request Forgery (SSRF)"},{"id":"CWE-614","name":"Sensitive Cookie in HTTPS Session Without 'Secure' Attribute"},{"id":"CWE-1004","name":"Sensitive Cookie Without 'HttpOnly' Flag"}],"labels":{"vendors":["Apache Software Foundation"],"products":["Apache Shiro"]},"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial"}},"nvd":{"description":"When Apache Shiro is used with the Jakarta EE integration module, the automatic form saving feature weakens the security of a form that is resubmitted after login.\nCookies set by the application during the resubmission could lose their security attributes, such as `Secure` and `SameSite`.\nIn addition, the resubmitted form data and cookies could be sent to an untrusted host.\nThis issue affects Apache Shiro from 2.0.0-alpha through 3.0.1, only when using `shiro-jakarta-ee` integration module with form saving enabled (the default).\n\nMitigation: Upgrade to version 3.0.2 or later, which no longer replays the form over the network, and avoids this class of issues entirely.\nAlternatively, you can set the `org.apache.shiro.form-resubmit-host` (String) and `org.apache.shiro.form-resubmit-port` (Integer) system properties to restrict the host and port that Shiro will connect to when resubmitting a form.","published":"2026-11-16","cwe":[{"id":"CWE-614","name":"Sensitive Cookie in HTTPS Session Without 'Secure' Attribute"},{"id":"CWE-918","name":"Server-side request forgery (SSRF)"},{"id":"CWE-1004","name":"Sensitive Cookie Without 'HttpOnly' Flag"}],"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#07338faa895cb2379d01b4c6df4363acfdc75c9c2c7e1d219c438b2e00dd88a5","checkedAt":"2026-11-16T23:39:03.167Z","changedAt":"2026-11-16T23:27:06.934Z","pocChangedAt":null}}