Withdraw GHSA-pqwr-phvv-v49f: source CVE-2024-7039 rejected by issuing CNA#8768
Open
Classic298 wants to merge 1 commit into
Open
Conversation
github-actions
Bot
changed the base branch from
main
to
Classic298/advisory-improvement-8768
July 22, 2026 19:16
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I am a maintainer of the affected project (
open-webui/open-webui). This advisory's source CVE, CVE-2024-7039, has been rejected by its issuing CNA (Protect AI / huntr), and both authoritative CVE sources reflect it:Since the underlying CVE has been rescinded, this GitHub-reviewed mirror should be withdrawn. It currently carries affected range
<= 0.3.8with no patched version, so it produces perpetual unfixable false positives in Dependabot and downstream scanners. There is no fixed version to assign; the correct correction is withdrawal.This change adds the OSV
withdrawntimestamp. For the record, as maintainer: the user-deletion endpoint is admin-only (get_admin_user; non-admins receive HTTP 401) and blocks self-deletion, so the claim reduces to an admin deleting users, which is intended admin capability and crosses no security boundary.