How severe is CVE-2026-56130?

CVE-2026-56130 has a CVSS 4.0 base score of 2.0, rated low severity.

Is CVE-2026-56130 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (13th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-56130?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-56130 have an EU (EUVD) identifier?

Yes. CVE-2026-56130 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-39229.

When was CVE-2026-56130 published?

CVE-2026-56130 was published on 2026-06-25.

CVE-2026-56130

CVE-2026-56130 is a low-severity vulnerability with a CVSS 4.0 base score of 2.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-294.

Key facts

Severity: Low (CVSS 4.0 base score 2.0)
EPSS exploit prediction: 0% (13th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-39229
Weakness: CWE-294
Published: 2026-06-25
Last modified: 2026-06-25

Description

"Remember me" cookie age is not verified on the server. This potentially allows an attacker to intercept a valid cookie and reuse it indefinitely, even after the configured expiration time has passed. This issue affects all Apache Shiro versions from 1.2.4 through 2.x, and 3.0.0-alpha-1, only when RememberMe functionality is enabled. Upgrade to version 3.0.0 or later, which fixes the issue.

Frequently asked questions

What is CVE-2026-56130?: "Remember me" cookie age is not verified on the server. This potentially allows an attacker to intercept a valid cookie and reuse it indefinitely, even after the configured expiration time has passed. This issue affects all Apache Shiro versions from 1.2.4 through 2.x, and 3.0.0-alpha-1, only when RememberMe functionality is enabled. Upgrade to version 3.0.0 or later, which fixes the issue.
How severe is CVE-2026-56130?: CVE-2026-56130 has a CVSS 4.0 base score of 2.0, rated low severity.
Is CVE-2026-56130 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (13th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-56130?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-56130 have an EU (EUVD) identifier?: Yes. CVE-2026-56130 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-39229.
When was CVE-2026-56130 published?: CVE-2026-56130 was published on 2026-06-25.

References

Other CWE-294 (Authentication Bypass by Capture-replay) vulnerabilities

CVE-2025-49752 — Critical (CVSS 10.0): Azure Bastion Elevation of Privilege Vulnerability
CVE-2026-11856 — Critical (CVSS 9.8): Successfully using libcurl to do a transfer to a specific HTTP origin (`hostA`) with **Digest** authentication and then…
CVE-2026-32987 — Critical (CVSS 9.8): OpenClaw before 2026.3.13 allows bootstrap setup codes to be replayed during device pairing verification in…
CVE-2025-67135 — Critical (CVSS 9.8): Weak Security in the PF-50 1.2 keyfob of PGST PG107 Alarm System 1.25.05.hf allows attackers to compromise access…
CVE-2025-65552 — Critical (CVSS 9.8): D3D Wi-Fi Home Security System ZX-G12 v2.1.1 is vulnerable to RF replay attacks on the 433 MHz sensor communication…
CVE-2024-38438 — Critical (CVSS 9.8): D-Link - CWE-294: Authentication Bypass by Capture-replay

Browse all CWE-294 (Authentication Bypass by Capture-replay) vulnerabilities →