Woodpecker before 3.15.0 registers the /api/orgs/lookup/*org_full_name endpoint without authentication middleware, and the LookupOrg handler unconditionally dereferences the session user (user.ForgeID, via ForgeFromUser) when selecting the forge to query. For an unauthenticated request session.User returns nil, so any unauthenticated HTTP request triggers a NULL pointer dereference in the handler. The panic is recovered by gin recovery middleware and the server continues serving (returning HTTP 500), but each request writes a multi-line panic stack trace to the error log. A low-bandwidth unauthenticated attacker can repeatedly probe the endpoint to flood the logs (about 37 lines per request), inflating disk usage and downstream log-ingestion cost and burying legitimate log events.
CVE-2026-58369
Score 5.3 from GitHub Security Advisory published 2026-06-30. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EPSS
- 28.3%
- KEV
- Not listed
Published
June 30, 2026
Last Modified
July 1, 2026
Advisory Details (4)
Auto-updated Jun 30, 2026Woodpecker < 3.15.0 - Unauthenticated NULL Pointer Dereference in /api/orgs/lookup Enables Log-Flooding Denial of Service | Advisories | VulnCheck
https://www.vulncheck.com/advisories/woodpecker-unauthenticated-null-pointer-dereference-in-api-orgs-lookup-enables-log-flooding-denial-of-service3.15.0
Patch available: woodpecker-ci/woodpecker v3.15.0
https://github.com/woodpecker-ci/woodpecker/releases/tag/v3.15.0Fix org lookup panic
Fix merged in woodpecker-ci/woodpecker PR #6652 on 2026-05-27 — awaiting tagged release
https://github.com/woodpecker-ci/woodpecker/pull/6652commit 1fbacac3a43b (woodpecker-ci/woodpecker)
Fix landed in woodpecker-ci/woodpecker commit 1fbacac3a43b — awaiting tagged release
https://github.com/woodpecker-ci/woodpecker/commit/1fbacac3a43b75b6e5a0a40a4f720a0017c62010Vendor Advisories for CVE-2026-58369(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 24× in last 7d / 24× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 13:53 UTCEG score recompute
- 2026-07-06 13:53 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 14:40 UTCEG score recompute
- 2026-07-05 14:39 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 15:22 UTCEG score recompute
- 2026-07-04 15:22 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 16:11 UTCEG score recompute
- 2026-07-03 16:10 UTCGHSA enrichment
- 2026-07-02 16:59 UTCEG score recompute
- 2026-07-02 16:59 UTCGHSA enrichment
- 2026-07-01 17:47 UTCEG score recompute
- 2026-07-01 17:47 UTCGHSA enrichment
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 18:33 UTCEG score recompute
- 2026-06-30 18:33 UTCGHSA enrichment
- 2026-06-30 18:32 UTCNVD updatefirst tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-58369?
When was CVE-2026-58369 disclosed?
Is CVE-2026-58369 actively exploited?
What is the CVSS score of CVE-2026-58369?
How do I remediate CVE-2026-58369?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-58369
Is Your Infrastructure Affected by CVE-2026-58369?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.