Tracking Anthropic-discovered vulnerabilities
VulnCheck's seven-month update tracks CVEs attributed to Anthropic's Project Glasswing.
Source-based brief · Editor review not recorded · See checks and limits ↓
One primary source; other links are context, not independent corroboration.
- Primary sourcevulncheck.com
- Discovery linkHacker News
- Linked in sourceTracking CVEs Attributed to Anthropic Researchers and Project Glasswing
- Linked in sourceObservations on Anthropic's Vulnerability Disclosure Ledger
- Linked in sourceThe Anthropic Glasswing Receipts Are Starting to Trickle In
- Linked in sourceAnthropic Credited CVEs
- Linked in sourcedisclosure ledger
- Linked in sourceOSS Scanner launch post
- Linked in sourceOSS Scanner
- Linked in sourceDaniel Stenberg
- Linked in sourceannounced
- Linked in sourcewrote
- Linked in sourceExploit & Vulnerability Intelligence
A community post points to the original link. Discussion and upvotes do not establish accuracy.
Open full article view →- Community discussion+5
- Fetched source page+30
- No editor link review+0
- Community link+0
This measures the stored source trail and editorial steps. It does not certify accuracy, peer review, or independent corroboration. Popularity adds no points.
View full scoring →Read the scoring rubric →What the source says
VulnCheck's seven-month update tracks CVEs attributed to Anthropic's Project Glasswing. It reports 442 attributable CVEs, roughly 0.5% of CVEs published this year, with two marked exploited in the wild. Anthropic's public ledger lists 37,966 findings, 7,349 made public, and 217 marked fixed. Duplicates (1,654) and withdrawals (419) have grown since September. Anthropic's OSS Scanner reports to curl were rated by the maintainer, who rejected 19 of 34 published reports as not vulnerabilities.
Claim explorer
Attribution, source and conditionsSource-stated points from the stored brief. Claim-level assessments have not been recorded.
This is a secondary analysis by VulnCheck from its own tracking repo and Anthropic's ledger; source claims, including the ledger's true positive rate and the curl counts, were not independently checked, and the author notes a possible ledger bug inflating disclosed counts.
This connects a source, an attributed statement and its qualifications. It does not establish that the claim is correct.
Questions worth asking
Open questions for further reportingWhat remains unconfirmed?
This is a secondary analysis by VulnCheck from its own tracking repo and Anthropic's ledger; source claims, including the ledger's true positive rate and the curl counts, were not independently checked, and the author notes a possible ledger bug inflating disclosed counts.
What material was available for this brief?
The recorded brief basis is fetched source page. These points are AINewsIQ paraphrases, not quotations or independent confirmations.
VulnCheck has tracked 442 CVEs attributable to Anthropic, about 0.5% of CVEs published this year, with two exploited in the wild.
Source: vulncheck.com ↗Stored source-based brief · key point 1 · AINewsIQ paraphraseOf Anthropic's 37,966 reported findings, 7,349 have been made public and 217 marked fixed.
Source: vulncheck.com ↗Stored source-based brief · key point 2 · AINewsIQ paraphraseBetween September and November, Anthropic added nearly 12,000 findings but recorded only 15 additional fixes.
Source: vulncheck.com ↗Stored source-based brief · key point 3 · AINewsIQ paraphrasecurl rejected 19 of 34 published Anthropic reports as not vulnerabilities and confirmed six as low severity.
Source: vulncheck.com ↗Stored source-based brief · key point 4 · AINewsIQ paraphraseLimits from the stored brief
This is a secondary analysis by VulnCheck from its own tracking repo and Anthropic's ledger; source claims, including the ledger's true positive rate and the curl counts, were not independently checked, and the author notes a possible ledger bug inflating disclosed counts.
This is a source-based abstract, not independent validation of the source's claims.
Evidence & sources
These links show where the signal came from and what the source page linked to. A linked page is context, not independent corroboration.
Related archive coverage
These relationships record a citation or topic overlap, not confirmation of the finding.
A community post points to the original link. Discussion and upvotes do not establish accuracy.
Timeline & updates
- Signal dated by source or discovery feed
This timestamp places the signal in the radar. It may be the discovery post date rather than the primary page's first publication date.
- Shared brief stored
AINewsIQ prepared one abstract from fetched source page.
Brief history · 1 retained version
These are changes to AINewsIQ’s own publication. Earlier history is unavailable unless recorded here. Complete retained versions are available to the editor.
- Version 1 · published
Source-based brief stored or updated. This does not establish that the publisher changed its page.
Automated record
Source observations · 1 recent captures
A changed capture means the extracted text differed. It can reflect page furniture or extraction changes; it does not establish a substantive correction. Source captures remain private.
Retained capture; no earlier comparison available.
New engagement snapshots do not mean the source itself changed. Source observations and AINewsIQ brief revisions are separate records.
Why this may matter
The figures bear on how much real security value AI-driven vulnerability discovery delivers versus how much triage work is shifted to open source maintainers. The disputed true positive rates bear directly on that question.
Limits and open questions
This is a secondary analysis by VulnCheck from its own tracking repo and Anthropic's ledger; source claims, including the ledger's true positive rate and the curl counts, were not independently checked, and the author notes a possible ledger bug inflating disclosed counts.
Organization-specific financial, security, and operational effects require the organization's own context and review.

Join the discussion
Have a different perspective or a question about the evidence? Discussion is free with a verified email account. Every comment is reviewed before publication.
No published comments yet.
New commenters: 2 submissions per 24 hours, at least 5 minutes apart, until 3 are approved. Discussion guidelines and moderation →