# CVE-2025-41082: HTTP Request/Response Smuggling in Altitude Communication Server

> Attackers can desynchronize HTTP requests via smuggling, enabling cache poisoning or security bypass in Altitude Communication Server.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jan 2026
- **Updated:** 26 Jan 2026
- **Also known as:** GHSA-67vw-jjgw-xcvq

## What is CVE-2025-41082?

CVE-2025-41082 is a medium-severity vulnerability in Altitude Communication Server, published on 26 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Illegal HTTP request traffic vulnerability (CL.0) in Altitude Communication Server, caused by inconsistent analysis of multiple HTTP requests over a single Keep-Alive connection using  Content-Length headers. This can cause a desynchronization of requests between frontend and backend servers, which could allow request hiding, cache poisoning or security bypass.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

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


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

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

## Is CVE-2025-41082 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41082 is a medium-severity vulnerability in Altitude Communication Server, published on 26 Jan 2026. 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-41082 in the wild and no public exploit code.

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

## Sources

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

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