Correct GHSA-49f7-whx5-4256: fix commit reverted; no released version remediates CVE-2026-58473#8740
Open
randomnimbus wants to merge 1 commit into
Conversation
github-actions
Bot
changed the base branch from
main
to
randomnimbus/advisory-improvement-8740
July 20, 2026 12:20
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.
Summary
This advisory (CVE-2026-58473) currently states the issue is fixed in cognee 1.2.0 (
details: "Cognee before 1.2.0 contains..."). That is not correct: the referenced fix was reverted six minutes after it merged, and no released version — up to and including current HEAD — contains it.This PR appends a clearly-attributed correction note to
detailsand adds the upstream tracking issue as a reference. It makes no change toaffected, severity, or CWE data.Public, referenceable evidence
d10b1b77e215(PR #3115)is_superuserguard to the settings routes (already referenced by this advisory)10971db1b0bdv1.2.0was tagged 2026-06-21, i.e. after the revert. Grepping the release trees of 1.2.0, 1.2.1, 1.2.2, 1.3.0, and 1.4.0, plusmain/devHEAD (as of 2026-07-19), theis_superuserguard is absent from all of them, and no later commit re-lands it. Commit ancestry is misleading here —d10b1b77e215is an ancestor of the release tags, but its change was immediately reverted, so a commit-presence check gives a false "fixed" signal.Upstream tracking issue (filed for maintainer confirmation of whether the revert was intentional): topoteretes/cognee#4146
Why this matters
Downstream consumers reading NVD / this advisory are told that upgrading to ≥ 1.2.0 remediates the issue. It does not — anyone who "remediated" by upgrading is running unpatched while believing otherwise.
Scope note
I've limited the change to the
detailsprose correction plus the tracking-issue reference, since those are the fields the false "fixed in 1.2.0" claim lives in. I've deliberately leftaffected(currently empty) to the GitHub Security team, since asserting the precise version-range/ecosystem mapping (no fixed version) is a larger call than the public-source correction this PR makes. Reported in good faith; contains only already-public information.