File size: 3,615 Bytes
a68859a 61977a2 a68859a 61977a2 a68859a 61977a2 a68859a 3d53d24 e8f0b64 a68859a 61977a2 a68859a 3d53d24 a68859a 61977a2 a68859a 61977a2 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 | # Werkzeug Windows Path Boundary Disclosure Record
Date: 2026-06-15
Status: sanitized public disclosure record in the responsible-disclosure lane.
## Summary
This is the public accountability record for a Werkzeug disclosure thread that
passed the 14-day no-response review date under our responsible-disclosure
rules.
Technical details are withheld here. This record exists so the disclosure
timeline is visible without publishing a reproduction recipe, private
correspondence, or raw technical material.
## What Was Reported Privately
- Reported area: Werkzeug path handling on Windows.
- Reported class: Windows/NTFS alternate-stream boundary handling across
Werkzeug path flows.
- Public status: no maintainer acknowledgement or routing response is visible in
the receipt source used for this lane.
The private report is about a specific Windows path interpretation boundary and
an alternate-stream exposure concern. This public record does not include the
triggering path form, route shape, file names, logs, or reproduction packet.
## Public Evidence
This record is backed by a metadata-only sent-email receipt and the canonical
cyber ledger. The email body and technical packet are not published here.
- Receipt ID: `gmail-sent-werkzeug-windows-ntfs-ads-20260525`.
- Canonical ledger row: `WERKZEUG-WINDOWS-NTFS-ADS-20260525`.
- Sent date recorded in Gmail metadata: 2026-05-25.
- Sent subject recorded in metadata: `Coordinated disclosure notice:
Windows/NTFS alternate-stream exposure chain involving Werkzeug paths`.
- Recipient label hash:
`5ec8ea9fe96296cf59a824c8e4234ef9530e9df8b9befa4dbd78cf5d173c8593`.
- Subject hash:
`ee75276fde3eeb6570f5253269a8acbb327665f456932457b2a215b76032a23d`.
- Visible thread-reply signal: no visible inbox label on the sent thread in the
Gmail metadata seed.
- Gmail metadata source SHA-256:
`059c2676fb828ec3388033369db2b8cdffda19b58604df90006ba722601013d4`.
- Sent-list image SHA-256:
`01a1a3f2ac0862bf2677a2346252c7731de9c1d5f9af8dbc643b42c839d6bfbb`.
- Cyber ledger SHA-256 at publication time:
`eef59c2a0433ff46aeb4ce163525284509319999055345b9ca1ed46ffa719675`.
## Evidence Boundary
The public evidence proves a disclosure record exists, identifies the reported
component and issue class, and records the no-response timing basis. It does not
publish the private email body, path form, route shape, raw logs, or technical
packet.
## Timeline
- First disclosure email sent: 2026-05-25.
- 14-day no-response review date: 2026-06-08.
- Published as a sanitized public disclosure record: 2026-06-15.
## What We Are Asking For
- Acknowledge receipt or point to the correct Pallets/Werkzeug handling route.
- State whether this is already known, fixed, duplicate, out of scope, or needs
the private packet resent.
- If more time is needed, say so and the public record can note that engagement
has started.
## Rules Applied
- The first disclosure email starts the review clock.
- If there is no acknowledgement or reply after 14 days, a sanitized public
record may be published after review.
- More detailed technical disclosure still requires separate human review.
- Private technical material remains reserved for an authorized security
responder.
## Limits
This public record establishes the disclosure timeline. Untrusted control is not
proven in this public record. Current-version behavior is not proven in this
public record. Maintainer validation, remediation status, final severity, and
affected-version scope are not proven in this public record. Private technical
material is retained for authorized responders.
|