# CVE-2025-45764: Weak cryptography in jsrsasign

> The jsrsasign library uses weak encryption key lengths, potentially allowing attackers to decrypt sensitive data.

- **Severity:** Low 3.2 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2025
- **Updated:** 26 Aug 2025
- **Also known as:** GHSA-qw4m-3r5p-h4wq

## What is CVE-2025-45764?

CVE-2025-45764 is a low-severity vulnerability in jsrsasign, published on 6 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

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

Weakness: CWE-326 (Inadequate Encryption Strength)

## Which versions are affected by CVE-2025-45764?


## How do I fix CVE-2025-45764?

No fix has been published for CVE-2025-45764 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-45764 being exploited?

There is no known exploitation of CVE-2025-45764 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-45764 and fix it if it is affected.

What it is: CVE-2025-45764 is a low-severity vulnerability in jsrsasign, published on 6 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-45764 in the wild and no public exploit code.

Affected product: jsrsasign. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-45764/ (Markdown: https://insights.sbomify.com/CVE-2025-45764/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-45764
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-45764
- OSV: https://osv.dev/vulnerability/CVE-2025-45764

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-45764/
Summaries are generated and may contain mistakes; the official description above is the record.