GitHub Security Advisories I filed and am credited on. 10 are GHSA-only credits with no CVE; together with 82 CVEs that makes 92 credited advisories. Each entry lists the project and the vulnerability type, and links to the advisory or my write-up.
If you need to report an AI or LLM flaw, start with my guide on how to disclose an AI vulnerability.
Security advisory for input validation bypass in webhook handling
Authentication bypass via spoofed client-IP headers (CWE-290/807; affects 6.1.0-7.15.3)
OPA body-inspection bypass via Content-Encoding: gzip (incomplete fix of GHSA-8qqm-fp2q-v734)
CVE-2026-46490 fix escapes attribute values but leaves attribute name/nameFormat unescaped; fixed 2.15.0
Non-constant-time API secret comparison + Paths[].Directory path traversal on /api/plan and /api/apply
system.run environment variable override leading to allowlist bypass / RCE
Admin account auto-seeded with default credentials admin/admin (CWE-798)
SSRF via merchant webhook URL in outgoing webhook delivery (full-read)
weed admin HTTP server exposes all write operations unauthenticated by default (CWE-306)
runtimeClassName can be set from pipeline steps without admin gate (incomplete fix of CVE-2026-61549); fixed 3.18.0
Authentication disabled by default in the generated API server (CVE-2026-47393).
Unguarded exec_module sinks in AgentsGenerator: prompt injection to code execution (CVE-2026-47398).
SSRF protection bypass via HTTP redirect and DNS rebinding in isSSRFSafeURL() (CVE-2026-43884).
SimpleAsyncHTTPClient forwards Authorization and Cookie headers across origins on a 3xx redirect (CVE-2026-49853). Fixed in 6.5.6.
Incomplete privilege-escalation patch: editUser() and updateUserRights() stay unguarded, so an admin with only edit_user can self-grant SuperAdmin (CVE-2026-56396). Fixed in 4.1.4.
An advisory under embargo is not a finding being hidden. It is a finding being held until the people who use the affected software can update without becoming targets in the window between disclosure and patch.
When a finding is under embargo, there is an open coordination channel with the upstream maintainer, an agreed disclosure date tied to the patch ship date, and — where the maintainer is unresponsive — a hard fallback at 90 days. It is not the absence of work; it's the presence of patience.
Once published, the row populates with the full advisory ID, the CVSS score, the affected versions, and the patch reference. Subscribe to the GitHub advisories feed if you want to be notified the moment that happens.