{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-58369 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-58369 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-58369 is a medium-severity vulnerability in woodpecker-ci woodpecker, published on 30 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-58369 and fix it if it is affected.\n\nWhat it is: CVE-2026-58369 is a medium-severity vulnerability in woodpecker-ci woodpecker, published on 30 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-58369 in the wild and no public exploit code.\n\nAffected product: woodpecker-ci woodpecker. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-58369/ (Markdown: https://insights.sbomify.com/CVE-2026-58369/index.md)","id":"CVE-2026-58369","markdown":"https://insights.sbomify.com/CVE-2026-58369/index.md","name":"CVE-2026-58369","record":{"aliases":["GHSA-xq6m-xxrf-h53q"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"CI/CD server","requires_auth":"none","summary":"Unauthenticated attackers can trigger a null pointer dereference in Woodpecker CI, causing log flooding and potential disk exhaustion.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Null dereference in woodpecker","id":"CVE-2026-58369","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Woodpecker \u003c 3.15.0 - GitLab Approval Gate Bypass via Spoofable Commit Author Name","id":"CVE-2026-58370"},"packages":[],"prev":{"headline":"Apache Doris: Improper Authentication in Frontend HTTP API","id":"CVE-2026-58319"},"products":["woodpecker"],"published":"2026-06-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-14","vendors":["woodpecker-ci"]},"summary":"Unauthenticated attackers can trigger a null pointer dereference in Woodpecker CI, causing log flooding and potential disk exhaustion.","url":"https://insights.sbomify.com/CVE-2026-58369/"}