VulnerabilityPublished 6 Aug 2025Updated 26 Aug 2025

CVE-2025-45764: jsrsasign · Inadequate Encryption Strength

Affects jsrsasignSource CVE Database V5

Not known to be exploited · CVSS 3.2 Low.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score

3.2Low

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

EPSS: 0.05% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
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: None: There is no loss of confidentiality within 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 6 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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
jsrsasign project jsrsasign	Affected =11.1.0	Fixed in–

AI-suggested

European organizations should first identify any usage of jsrsasign v11.1.0 within their software stacks, especially in critical applications involving digital signatures or cryptographic verification. Since no official patches are currently available, organizations should consider the following specific mitigations: 1) Replace or upgrade jsrsasign to a later version if available, or switch to alternative cryptographic libraries with stronger default encryption parameters. 2) Enforce strict local access controls and monitoring to prevent unauthorized local access that could enable exploitation. 3) Conduct thorough cryptographic audits to verify key lengths and encryption parameters used in applications, ensuring they meet current security standards. 4) Implement additional application-level integrity checks and multi-factor verification for critical cryptographic operations to mitigate risks from potential signature forgery. 5) Stay informed on updates from the jsrsasign project and CVE authorities regarding dispute resolution and patch releases. 6) For environments where upgrading is not immediately feasible, consider compensating controls such as network segmentation and enhanced logging to detect suspicious activities related to cryptographic operations.

Description

jsrsasign v11.1.0 was discovered to contain weak encryption. NOTE: this issue has been disputed by a third party who believes that CVE IDs can be assigned for key lengths in specific applications that use a library, and should not be assigned to the default key lengths in a library. This dispute is subject to review under CNA rules 4.1.4, 4.1.14, and other rules; the dispute tagging is not meant to recommend an outcome for this CVE Record.

Impact

For European organizations, the potential impact of this vulnerability is primarily on the integrity of cryptographic operations relying on jsrsasign v11.1.0. Since jsrsasign is used in various web applications and services for digital signature verification and cryptographic functions, weak encryption strength could allow attackers with local access to manipulate or forge signatures, potentially undermining trust in data authenticity. However, the requirement for local access and high attack complexity reduces the likelihood of widespread exploitation. The lack of confidentiality or availability impact further limits the threat. Organizations in sectors relying heavily on cryptographic assurances, such as finance, government, and critical infrastructure, could face risks if they use the vulnerable library version without additional safeguards. Given the dispute over the vulnerability's validity and the absence of known exploits, the immediate risk to European entities is low but should not be ignored, especially in environments where local access controls are weak or where cryptographic integrity is paramount.

Summary

CVE-2025-45764 identifies a vulnerability in version 11.1.0 of the jsrsasign project, a widely used JavaScript library for cryptographic signing and verification. The vulnerability is categorized under CWE-326, which relates to inadequate encryption strength. Specifically, the issue concerns the use of weak encryption parameters or key lengths within the library's default cryptographic implementations. This could potentially allow attackers to compromise the integrity of cryptographic operations, such as digital signatures, by exploiting weaker-than-expected encryption strength. However, the vulnerability's existence and scope have been disputed by a third party, who argues that CVE assignments should be tied to specific applications using the library with weak key lengths rather than the library's default key lengths themselves. The CVSS v3.1 base score is 3.2 (low severity), reflecting that exploitation requires local access (AV:L), high attack complexity (AC:H), no privileges (PR:N), and no user interaction (UI:N). The impact is limited to integrity loss without affecting confidentiality or availability, and the scope is changed (S:C), indicating that the vulnerability affects components beyond the vulnerable library itself. No known exploits are currently reported in the wild, and no patches have been published yet. The dispute and low CVSS score suggest that while the vulnerability exists, its practical impact and exploitability are limited, especially given the high attack complexity and local access requirements.

CWE-326Inadequate Encryption Strength (opens in a new tab)
Class weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.
Architecture and Design
Use an encryption scheme that is currently considered to be strong by experts in the field.
OWASP Cheat Sheets
Cryptographic Storage (opens in a new tab)
Key Management (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.3 (opens in a new tab)
V6.2.7 (opens in a new tab)
V6.2.4 (opens in a new tab)
Attack patterns
Encryption Brute Forcing (opens in a new tab)
Brute Force (opens in a new tab)
Protocol Analysis (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Aug 2025, 00:41 UTC

WeaknessesCWE-326

Technical details

References

Community reviews

Related threats