Skip to content

Audit + correct the CVE registry (0.23.0) - #27

Merged
autonomyproof merged 1 commit into
mainfrom
fix/cve-registry-audit
Aug 18, 2026
Merged

Audit + correct the CVE registry (0.23.0)#27
autonomyproof merged 1 commit into
mainfrom
fix/cve-registry-audit

Conversation

@autonomyproof

Copy link
Copy Markdown
Owner

Re-verified every _CVE_DB entry against NVD/GitHub Advisories. All 8 CVE IDs are genuine. Fixed two inaccuracies: CVE-2025-3108 llama-index range (was flagging unaffected versions) and CVE-2025-48889 gradio summary/MITRE. 642 tests, corpus 1.000/1.000. Bumps 0.22.0->0.23.0.

Re-verified every _CVE_DB entry against NVD / GitHub Advisories. All 8 CVE IDs are genuine
published advisories; two records had inaccuracies now fixed:

- CVE-2025-3108 (llama-index-core): affected range was >=0.11.15,<0.12.41 but the published
  advisory is 0.12.27-0.12.40. Versions 0.11.15-0.12.26 were being flagged in error
  (false positive). Corrected to >=0.12.27,<0.12.41.
- CVE-2025-48889 (gradio): summary claimed 'arbitrary file read / secret theft'; the advisory
  is an unauthorized file *copy* via path manipulation (DoS) — attackers cannot read the
  copied files. Corrected the summary; MITRE mapping T1552 -> T1499.

The langchain-core (CVE-2025-68664, CVE-2026-44843) and gradio (CVE-2025-48889) advisories
that the benchmark found pinned in real repos are all genuine and correctly ranged, so those
findings stand. 642 tests, 100% coverage, corpus 1.000/1.000. Bumps 0.22.0 -> 0.23.0.

Signed-off-by: AutonomyProof <info@autonomyproof.io>
@autonomyproof
autonomyproof merged commit 14a3f83 into main Aug 18, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant