VulnerabilityPublished 25 May 2026Updated 12 Nov 2026

CVE-2026-48589: Apache Shiro’s Jakarta EE module used the HTTP Referer header in certain cases to issue redirect

Affects shiroSource GCVE Database

Compare

Not known to be exploited · CVSS 5.4 Medium.

Data as of 12 Nov 2026, 19:55 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 May 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 12 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10shiro`pkg:deb/ubuntu/shiro?arch=source&distro=stonking`Other threats	Affected =1.3.2-6ubuntu2	Fixed in–
Ubuntu 26.04 LTSshiro`pkg:deb/ubuntu/shiro?arch=source&distro=resolute`Other threats	Affected =1.3.2-6ubuntu1 =1.3.2-6ubuntu2	Fixed in–
Ubuntu 25.10shiro`pkg:deb/ubuntu/shiro?arch=source&distro=questing`Other threats	Affected =1.3.2-6ubuntu1	Fixed in–
Ubuntu Pro 24.04 LTSshiro`pkg:deb/ubuntu/shiro?arch=source&distro=esm-apps/noble`Other threats	Affected =1.3.2-5 =1.3.2-5ubuntu0.24.04.1~esm1	Fixed in–
Ubuntu 22.04 LTSshiro`pkg:deb/ubuntu/shiro?arch=source&distro=jammy`Other threats	Affected =1.3.2-4 =1.3.2-5	Fixed in–
Ubuntu 20.04 LTSshiro`pkg:deb/ubuntu/shiro?arch=source&distro=focal`Other threats	Affected =1.3.2-4 =1.3.2-4ubuntu0.1 =1.3.2-4ubuntu0.2	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, users should consider implementing additional validation or filtering of redirect targets derived from client-controlled headers in their applications using the shiro-jakarta-ee module.

Description

Apache Shiro's Jakarta EE module improperly uses the HTTP Referer header to determine redirect targets after user login. Insufficient validation of this client-controlled header can allow attackers to influence redirect destinations in affected versions. This vulnerability affects Apache Shiro versions from 2.0-alpha to 2.2.0 and 3.0.0-alpha-1 when using the shiro-jakarta-ee integration module.

Impact

An attacker can influence the redirect target after user login by manipulating the HTTP Referer header. This can lead to redirect-based attacks such as phishing or redirecting users to malicious sites. The impact is limited to confidentiality and integrity with no direct availability impact. The CVSS score of 5.4 (medium severity) reflects the moderate risk due to the need for user interaction and limited privileges required.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Nov 2026, 19:55 UTC

Technical details

References

Community reviews

Related threats