# CVE-2026-65370: Other in servicetalk

> Attackers can perform request smuggling via malformed Transfer-Encoding headers in ServiceTalk HTTP/1.x, bypassing security controls.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-56h2-h3h4-m9x6

## What is CVE-2026-65370?

CVE-2026-65370 is a high-severity vulnerability in Apple servicetalk, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ServiceTalk HTTP/1.x incorrectly handles malformed Transfer-Encoding which could result in request smuggling attacks. This vulnerability is addressed in servicetalk version 0.42.65.

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

## Which versions are affected by CVE-2026-65370?

It affects 1 product.


Products: Apple Servicetalk.

## How do I fix CVE-2026-65370?

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

## Is CVE-2026-65370 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-65370 and fix it if it is affected.

What it is: CVE-2026-65370 is a high-severity vulnerability in Apple servicetalk, published on 12 Aug 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-2026-65370 in the wild and no public exploit code.

Affected product: Apple servicetalk. 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-2026-65370/ (Markdown: https://insights.sbomify.com/CVE-2026-65370/index.md)
```

## Sources

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

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