CVE-PATCHBAY-2026-0001· withdrawnWITHDRAWN: initial finding was a false positive (product URL slug matched OpenAI key regex)
This advisory has been WITHDRAWN. The underlying SECRET-001 finding against the target was a false positive produced by an overly loose regex: our openai-key pattern allowed dashes in the secret body, so a product URL slug matching the shape `sk-<two letters>-<three letters>-<nineteen digits>` inside committed catalog audit JSON files tripped it. Real OpenAI API keys do not contain hyphens or underscores in their secret body; the regex has been tightened to /\bsk-(?:proj-)?[A-Za-z0-9]{40,}\b/g in audit-core, which rejects the slug and every similar false positive found in the 2k deep crawl (test fixtures containing `must-not-surface` idioms, slug-style identifiers of the form `sk-<word>-<word>-<word>`, and Slack placeholders of the form `xoxb-your-<word>-<word>-token`). See evidence.redactedMatches below.
Finding
Check SECRET-001 · n/a — withdrawn
Evidence
Redacted shape of each false-positive match (not verbatim, so this file itself does not trip secret scanners): (1) sk-ct-sys-<nineteen digits> — product URL slug, BuyWhere; (2) sk-live-secret-material — test fixture string literal, Cotal; (3) sk-fixture-secret-... — smoke test fixture, Cotal; (4) sk-hynix-ddr5-memory-kit — example slug in code comment, Pomerado; (5) xoxb-your-<...>-token — env.example placeholder, Fodda x6.
Fix
n/a — withdrawn. The underlying scanner bug has been fixed in audit-core: tighter openai-key regex, tighter slack-bot-token regex (three-segment numeric structure), and expanded example-pattern filter covering `your-<word>-token`, `fixture`, `mock`, and `must-not-surface` idioms. See packages/audit-core/src/probe/directory.ts.
References
Credit
Discovered by: patchbay crawler, 2026-11-13 MVP crawl
Reported by: Sarah Vogel, patchbay
Published 2026-11-13 · Last modified 2026-11-13