# CVE-2025-46833: Programs/P73_SimplePythonEncryption.py has weak cryptographic key

> Weak RSA key size in a Python encryption example allows attackers to decrypt data via brute force, compromising confidentiality.

- **Severity:** Medium 4.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 May 2025
- **Updated:** 8 May 2025
- **Also known as:** GHSA-5h26-2c6g-4ch4

## What is CVE-2025-46833?

CVE-2025-46833 is a medium-severity vulnerability in ShashikantSingh09 python-progrrames, published on 8 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Programs/P73_SimplePythonEncryption.py illustrates a simple Python encryption example using the RSA Algorithm. In versions prior to commit 6ce60b1, an attacker may be able to decrypt the data using brute force attacks and because of this the whole application can be impacted. This issue has been patched in commit 6ce60b1. A workaround involves increasing the key size, for RSA or DSA this is at least 2048 bits, for ECC this is at least 256 bits.

Weakness: CWE-326 (Inadequate Encryption Strength)

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


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

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

## Is CVE-2025-46833 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-46833 is a medium-severity vulnerability in ShashikantSingh09 python-progrrames, published on 8 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-46833 in the wild and no public exploit code.

Affected product: ShashikantSingh09 python-progrrames. 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-46833/ (Markdown: https://insights.sbomify.com/CVE-2025-46833/index.md)
```

## Sources

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

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