1sealsemantic last-mile verification

Research / Finding

bound request-body reads in the machine map endpoint

F-HEADSCALE-001-001

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
juanfont/headscaleReported fixjuanfont/headscale

bound request-body reads in the machine map endpoint

fixed publicly
details
Finding IDs
F-HEADSCALE-001-001
Status
fixed publicly
Reported via
security contact
Note
the public fix is available in Headscale v0.29.0 and v0.29.1. no public GHSA was observed, so this is tracked as a landed fix rather than a published advisory.

F-HEADSCALE-001-001: Resource limits. Machine-map request bodies are not bounded before processing. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-HEADSCALE-001-001

Security area (1seal assessment): Availability. Machine-map request bodies are not bounded before processing. 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.