CVE-2022-25898

What it is

The package jsrsasign before 10.5.25 are vulnerable to Improper Verification of Cryptographic Signature when JWS or JWT signature with non Base64URL encoding special characters or number escaped characters may be validated as valid by mistake. Workaround: Validate JWS or JWT signature if it has Base64URL and dot safe string before executing JWS.verify() or JWS.verifyJWT() method.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. High risk of service disruption.

Exploit odds

1.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2022-07-01 20:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-22 03:18 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.2% in the next 30 days (EPSS).
• Severity: 7.7 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2022-07-01 20:15 UTC

Last modified

2026-06-22 03:18 UTC

Exploit probability

1.2% · EPSS, next 30 days

Weakness

CWE-347

Record status

Modified

Affected

• Kjur Jsrsasign < 10.5.25

Attack profile CVSS 3.1 · 7.7

Attack vector

Network

Complexity

High

Privileges needed

Low

User interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2022-25898.md and follow it. Check whether this project is affected by CVE-2022-25898. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge