# OSV-2026-610: Memcpy-param-overlap in htx_replace_blk_value

> A memory corruption vulnerability in the HTTP header replacement logic allows remote attackers to cause a denial of service via crafted requests.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2026

## What is OSV-2026-610?

OSV-2026-610 is a memory corruption vulnerability in haproxy, published on 22 Apr 2026. It can be exploited over the network, with no action from the victim.

### Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=504612570

```
Crash type: Memcpy-param-overlap
Crash state:
htx_replace_blk_value
http_replace_header_value
http_scheme_based_normalize
```

## Which versions are affected by OSV-2026-610?

1 open source package ship an affected version, including haproxy.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `haproxy` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2026-610?

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

## Is OSV-2026-610 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2026-610 and fix it if it is affected.

What it is: OSV-2026-610 is a memory corruption vulnerability in haproxy, published on 22 Apr 2026. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of OSV-2026-610 in the wild and no public exploit code.

Affected packages and fixed versions:
- haproxy (OSS-Fuzz): affected all versions; no fix listed

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/OSV-2026-610/ (Markdown: https://insights.sbomify.com/OSV-2026-610/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2026-610

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