1sealsemantic last-mile verification

Research / Finding

docs: clarify proxy cache trust boundary for upstream token-service discovery

F-HARBOR-REALM-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
goharbor/website #706Security PRgoharbor/website

docs: clarify proxy cache trust boundary for upstream token-service discovery

merged
details
Finding IDs
F-HARBOR-REALM-001
Status
merged
Reported date
Rationale
clarifies the proxy cache trust boundary to reduce the risk of misconfiguration around token-service discovery.
PR opened by
@1seal
PR state observed
closed; GitHub merged: true; 2026-09-24
PR observation basis
Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed.
Contribution boundary
@1seal opened this PR; this alone does not establish sole code authorship.

F-HARBOR-REALM-001: Outbound request trust. The documented realm-trust issue concerns credential-bearing outbound destinations. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-HARBOR-REALM-001

Security area (1seal assessment): Authorization. Documentation clarifies which upstream token-service endpoints may receive registry credentials; this is trust-boundary guidance, not a code fix. Reviewed 21 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.