Skip to content

Standard

CWE

Common Weakness Enumeration: a community-maintained taxonomy of software and hardware weakness types, used to classify and prioritize vulnerabilities.

Known aliases

  • Common Weakness Enumeration
  • CWE
  • {cwe}
  • CWE Top 25

Current stories

buildOne report1 publisher

Texas Tech study finds coding-agent revert rates range from 6.1% to 14.5% by vendor

Obada Kraishan of Texas Tech tracked 37,623 GitHub pull requests and found 90-day revert rates of 6.1% for OpenAI Codex and 14.5% for Devin. A pooled 'AI code' rate from that sample mostly measures Codex, so each tool needs its own numbers.

Publishers:dev.to

Reality

Evidence55
Adoption
Not scored
Hype gap+10
Incentives35
Confidence50
securityConfirmed3 publishers

Cisco's control planes are the exposure: four criticals in Crosswork, four in Secure Workload

Three of the Crosswork flaws score a flat 10.0, and Cisco says each CVE bundles several underlying defects. No exploitation reported in the wild so far.

Perspective Coverage

3 publishers
Builder
Builder 28%
Operator
Operator 62%
Investor
Investor 10%

Reality

Evidence72
Adoption
Not scored
Hype gap+10
Incentives40
Confidence70
securityOne report1 publisher

Safe code fooled all 12 models AWS tested in its Deception Benchmark

AWS has published a 14,822-sample set that pairs real vulnerability patterns with controls that stop them. With direct prompting the 12 models it scored flagged between 41% and 99% of safe samples as exploitable.

Reality

Evidence58
Adoption18
Hype gap+15
Incentives65
Confidence57
securityOne report1 publisher

CISA asks buyers to make eliminated vulnerability classes a contract condition

Its review of fiscal 2024 and 2025 says opportunistic scanning of known, internet-exposed flaws drove most compromises. The fix, it argues, belongs to software producers, not to defenders patching faster.

Reality

Evidence58
Adoption18
Hype gap+15
Incentives55
Confidence55
buildOne report1 publisher

Telling a model that a scanner already flagged the code buys you a rubber stamp

A developer ran 200 flagged snippets past two frontier models with identical prompts. One cleared 51% of the false alarms; the other cleared 20% and agreed with 90% of what it saw. The countermeasures are a model property.

Publishers:dev.to

Reality

Evidence24
Adoption9
Hype gap+32
Incentives46
Confidence33
buildOne report1 publisher

The refusal came back labelled "infeasible": reading a planner/critic jailbreak test

PlannerCritic's author tried to inject his own engine. The blocks arrived as feasibility verdicts rather than safety strings, which is a design worth copying and a limit worth reading closely.

Publishers:dev.to

Reality

Evidence44
Adoption12
Hype gap+24
Incentives72
Confidence41
buildOne report1 publisher

Anthropic's GitHub scanner goes Enterprise-only, and the model behind it is not established

The hosted Claude Security beta bills as ordinary Claude usage with no platform fee, while Mythos 5 stays with vetted partners. What runs the Enterprise scans is not settled by the sources.

Publishers:runtimewire.com

Reality

Evidence38
Adoption33
Hype gap+22
Incentives72
Confidence40
productOne report1 publisher

CodeQL 2.26.3 treats workflow files as code, and cache poisoning as a finding you must triage

GitHub's August release retunes Actions queries for cache poisoning, output clobbering and untrusted checkouts. Most of the work went into cutting false positives, not adding coverage.

Publishers:devops.com

Reality

Evidence58
Adoption28
Hype gap+6
Incentives44
Confidence60
productOne report1 publisher

The cheapest model scored 10 out of 100: assistant choice is now a code-security decision

A Secure Code Warrior and RMIT study of six frontier models across 11 frameworks found no universal winner and no link between token cost and secure output.

Publishers:devops.com

Reality

Evidence48
Adoption
Not scored
Hype gap+20
Incentives68
Confidence40