1sealsemantic last-mile verification

Research / Finding

uhv: use-after-free read in sanitizeHeadersWithUnderscores with duplicate underscore headers

F-ENVOY-001-003

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Read the evidence · View in research browse

Recorded evidence

—score not recorded
envoyproxy/envoyReported fixenvoyproxy/envoy

uhv: use-after-free read in sanitizeHeadersWithUnderscores with duplicate underscore headers

fixed publicly via issue closure
details
Finding IDs
F-ENVOY-001-003
Status
fixed publicly via issue closure
Reported via
public GitHub issue
Note
public issue #44032 was opened by @1seal and describes a UHV use-after-free read in HeaderValidator::sanitizeHeadersWithUnderscores() when duplicate underscore headers are dropped via non-owning string_view references. the issue is closed and cross-references #44086; tracked as fixed based on the public issue status, without a separate CVE/GHSA or release claim.

F-ENVOY-001-003: Memory safety. Duplicate underscore headers trigger a use-after-free read during sanitization. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-ENVOY-001-003

Security area (1seal assessment): Memory safety. Duplicate underscore headers trigger a use-after-free read during sanitization. Reviewed 24 Sep 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.