# CVE-2025-14501: Sante PACS Server HTTP Content-Length Header Handling NULL Pointer Dereference Denial-of-Service Vulnerability

> Remote attackers can cause a denial-of-service condition in Sante PACS Server by exploiting a null pointer dereference in HTTP header handling without authentication.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Dec 2025
- **Updated:** 29 Dec 2025
- **Also known as:** GHSA-7pvc-gq25-w4q2

## What is CVE-2025-14501?

CVE-2025-14501 is a high-severity vulnerability in Sante PACS Server, published on 23 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sante PACS Server HTTP Content-Length Header Handling NULL Pointer Dereference Denial-of-Service Vulnerability. This vulnerability allows remote attackers to create a denial-of-service condition on affected installations of Sante PACS Server. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the handling of HTTP Content-Length header. The issue results from the lack of proper validation of a pointer prior to accessing it. An attacker can leverage this vulnerability to create a denial-of-service condition on the system. Was ZDI-CAN-26770.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

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

## Is CVE-2025-14501 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14501 is a high-severity vulnerability in Sante PACS Server, published on 23 Dec 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-14501 in the wild and no public exploit code.

Affected product: Sante PACS Server. 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-14501/ (Markdown: https://insights.sbomify.com/CVE-2025-14501/index.md)
```

## Sources

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

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