# CVE-2025-24946: Denial of service in picoquic

> Remote attackers can cause server CPU exhaustion via Hash DoS by exploiting a weak hash function in the connection management table.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2025
- **Updated:** 20 Feb 2025
- **Also known as:** GHSA-m6hh-vp2v-rm5m

## What is CVE-2025-24946?

CVE-2025-24946 is a medium-severity denial of service vulnerability in privateoctopus picoquic, published on 20 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The hash table used to manage connections in picoquic before b80fd3f uses a weak hash function, allowing remote attackers to cause a considerable CPU load on the server (a Hash DoS attack) by initiating connections with colliding Source Connection IDs (SCIDs).

Weakness: CWE-407 (Inefficient Algorithmic Complexity)

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


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

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

## Is CVE-2025-24946 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-24946 is a medium-severity denial of service vulnerability in privateoctopus picoquic, published on 20 Feb 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-24946 in the wild and no public exploit code.

Affected product: privateoctopus picoquic. 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-24946/ (Markdown: https://insights.sbomify.com/CVE-2025-24946/index.md)
```

## Sources

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

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