Skip to main content
Menu
CVEs

CVE

Apache Shiro Jakarta EE form data exposure in saved form replay

CVE-2026-88019EUVD-2026-126381GHSA-J2X3-W3R4-J8JJ

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/S:N/AU:N/R:U/V:D/RE:L/U:Amber

6.0MediumCNA
Exploited
No known exploitation
Fix
Fixed in 3.0.2
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 3.0.2.

Published
Last modified
Reference
Last checked
23/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

Apache Shiro's Jakarta EE integration module, when its default form-saving feature is enabled, can resubmit a saved form after login in a way that strips cookies of their `Secure` and `SameSite` protections and sends the form data and cookies to an untrusted host. A remote attacker who needs no login can exploit this when a user takes an action, exposing form data and weakening cookie security.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original 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. Cookies set by the application during the resubmission could lose their security attributes, such as Secure and SameSite. In addition, the resubmitted form data and cookies could be sent to an untrusted host. This 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).

Mitigation: Upgrade to version 3.0.2 or later, which no longer replays the form over the network, and avoids this class of issues entirely. Alternatively, 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.

cve.now Index

23Pcve.now Index 23 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
  • Reach10/20Affects Maven packages
  • Severity6/10CVSS 6.0
  • No patch0/5No signal

What would change the score

  • Would score about 78 if added to CISA KEV
  • Would score about 73 if CISA's SSVC rates exploitation active
  • Would score about 38 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 3.0.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-88019 (Apache Shiro: Saved form replay may weaken cookie security and expose form data), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-88019 (entry last updated 2026-11-16):
Affected:
- Maven package org.apache.shiro:shiro-jakarta-ee: from 2.0.0-alpha-0, fixed in 3.0.2
Fixed versions: 3.0.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-88019 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-88019 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Maven): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread/fvlsfo9zoz5rqqn15pz4b72nkjbjmfw7
- http://www.openwall.com/lists/oss-security/2026/11/14/3
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-88019
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-88019"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • From 2.0.0-alpha-0 · fixed in 3.0.2

    Fixed in 3.0.2 (released Nov 8, 2026, 8 days before disclosure).

    The latest release, 3.0.2, is not affected.

Evidence 4

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Write-ups · 1

Establishes: Technical detail and context.

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-88019

Is CVE-2026-88019 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-88019?

org.apache.shiro:shiro-jakarta-ee (Maven): from 2.0.0-alpha-0 before 3.0.2.Source: cve.now feed data

How do I fix CVE-2026-88019?

Upgrade to a fixed version: 3.0.2.Source: cve.now feed data