1sealsemantic last-mile verification

Research / Finding

Don't modify http.DefaultTransport

F-BOULDER-009

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
letsencrypt/boulder #8641Credited fixletsencrypt/boulder

Don't modify http.DefaultTransport

merged
details
Finding IDs
F-BOULDER-009
Status
merged
Recorded credit
thanks to Oleh Konko (@1seal) for reporting this issue (comment by @aarongable).

F-BOULDER-009: General hardening / testing. The recorded change avoids mutation of shared HTTP transport defaults; a narrower defect is not established here. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-BOULDER-009

Security area (1seal assessment): Identity. Cloning the HTTP transport confines InsecureSkipVerify and other TLS options to the observer client instead of mutating global defaults. This is identity-verification configuration hardening, not proof of a reachable exploit. 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.