factcheck: credential-management-ai-agents#283
Open
bicced wants to merge 1 commit into
Open
Conversation
…bution, CVE-2025-29927 description, Vault/Infisical stars, Vault license, CVE-2026-39829 framing
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
Fact-check & improvement: learn/credential-management-ai-agents
Corrections
CVE-2024-34359 misattribution (CRITICAL) — was attributed to "LangChain, CVSS 9.8, credential leakage via prompt injection". Corrected: CVE-2024-34359 is a
llama-cpp-pythonvulnerability (Jinja2 SSTI via unsandboxed model metadata rendering, CVSS 9.6), not a LangChain CVE and not a credential leakage via prompt injection. The description has been corrected throughout the page (lede, CVE section, FAQ). Source: NVD CVE-2024-34359, GHSA-56xg-wfcc-g829CVE-2025-29927 description — was "env-var secrets exposed via header bypass". Corrected: the CVE is a middleware authorization bypass (
x-middleware-subrequestheader) in Next.js, not specifically about env-var credential exposure. Applications using Next.js middleware to gate protected routes (including AI agent backends) were affected. CVSS 9.1 confirmed correct. Source: NVD CVE-2025-29927HashiCorp Vault stars — was 35,736, corrected to 35,763. Source: GitHub API (
hashicorp/vault, retrieved 2026-06-11)HashiCorp Vault license consistency — first mention introduced Vault as "MPL-2.0" but the page later correctly notes the August 2023 BSL license change. Changed first mention to "BSL" for consistency throughout. Source: GitHub license field (
hashicorp/vault)Infisical stars — was 27,236, corrected to 27,296. Source: GitHub API (
Infisical/infisical, retrieved 2026-06-11)CVE-2026-39829 framing — was described as "RSA key size cap in the SSH secrets engine". Corrected: CVE-2026-39829 is a golang/crypto library DoS vulnerability (unbounded RSA modulus in SSH key parsing). Vault v2.0.2 addressed it at the application level by applying size limits. "SSH secrets engine" is imprecise; the CVE is in the underlying Go crypto library. Source: NVD CVE-2026-39829, Vault v2.0.2 release notes
Verified Correct (no change)
Unverifiable (flagged, not changed)
Quality
last_updatedto 2026-06-11Opened by fact-checker (OpenLegion). Human review + merge. Validator runs in CI.