Search: “vulnerability-analysis”

The Vulnerability Gap: Why Discovery Is Outrunning Repair

Dark Reading argues AI-accelerated vulnerability discovery and tightening regulation are widening the gap between flaw discovery and repair capacity.

The article argues that AI tooling is increasing the pace at which vulnerabilities are discovered while remediation capacity has not kept up, creating a growing backlog. It frames this widening 'vulnerability gap', combined with a tightening regulatory environment, as an all-hands-on-deck moment for security teams. The piece is analysis and opinion rather than disclosure of a specific flaw.

Dark Reading·Aug 24, 14:00 UTC · 22d agoIndustry

VEX-Bench: Benchmarking LLM Agents for Assessing Exploitability of Software Supply Chain Vulnerabilities

Introduces VEX-Bench, 75 expert-labeled real-world cases testing whether LLM agents can assess supply chain vulnerability exploitability; frontier models reach about 80% F1.

VEX-Bench is the first benchmark evaluating LLM agents on assessing whether upstream dependency vulnerabilities are exploitable in downstream projects, with 75 real-world expert-labeled cases across Python, Java, and Go mined from GitHub. Nine models across three agent harnesses were evaluated; GPT-5.5 and Claude Opus 4.6 reach approximately 80% F1 on binary vulnerability-status classification, but only GPT-5.5 surpasses 70% macro-F1 on fine-grained justification classification. The gap highlights the difficulty of moving beyond binary exploitability calls to explaining exploitability reasons, unlike prior benchmarks targeting zero-day settings.

arXiv cs.CR·Sep 7, 22:52 UTC · 8d agoResearch1

Building a risk-based vulnerability management program that scales

Asimily CEO Shankar Somasundaram outlines a risk-based vulnerability management approach using inventory, attack paths, KEV and EPSS data.

In a Help Net Security video, Asimily CEO Shankar Somasundaram argues patching everything is infeasible as AI-driven attacks inflate vulnerability counts, with one customer finding a thousand unknowns for each known one. He recommends building a full inventory of devices, applications, and data flows, mapping attack paths for reachability, and prioritizing with KEV, EPSS, and business impact. Mitigations include patching, virtual patching via NACs and firewalls, segmentation, and configuration snapshots to detect drift.

Help Net Security·Aug 24, 04:21 UTC · 23d agoIndustry

Introducing Continuous Vulnerability Assessment: Real-Time Defense for the AI Threat Era

Wiz launched Continuous Vulnerability Assessment (CVA), alerting customers to exposure against newly published vulnerabilities in real time.

Wiz introduced Continuous Vulnerability Assessment, a capability that detects exposure to newly published vulnerabilities the moment they are disclosed. The company positions CVA as real-time defense for the AI threat era, reducing the window between disclosure and remediation decisions. The item is a vendor product announcement with no incident details.

Wiz Blog·Sep 1, 10:54 UTC · 15d agoTools

CISA Vulnerability Review

CISA's Vulnerability Review finds most compromises exploit exposed, well-known flaws due to basic security failures, based on FY2024-2025 data.

The CISA Vulnerability Review analyzes CISA and open-source data from fiscal years 2024 and 2025. It concludes most compromises do not rely on advanced techniques; threat actors scan the internet for exposed, well-known software vulnerabilities. CISA urges organizations to address underlying weaknesses and prioritize vulnerabilities for remediation based on the risk they pose.

CISA Advisories·Aug 26, 12:00 UTC · 20d agoAdvisory

Can your coding style predict whether your code is vulnerable?

University of Massachusetts Dartmouth researchers present VulStyle, a stylometry-based vulnerability detector that also exposes benchmark reliability problems.

VulStyle combines stylometric features with syntax-tree structure and source tokens, pre-trained on about 4.9 million functions across seven programming languages and fine-tuned on five vulnerability detection datasets. It beat token-only detectors on some benchmarks but its F1 drops sharply on DiverseVul, which the authors link to noisy labels inflating reported performance across popular datasets. The authors argue style-aware detection should be harder to evade but did not test this empirically, and they note that uniform LLM-generated code may strip away the individual developer style the model depends on.

Help Net Security·Aug 24, 04:21 UTC · 23d agoResearch1

An Empirical Analysis of ReDoS Vulnerabilities and ReDoS Detection Tools

Study of NVD data finds ReDoS vulnerabilities growing more prevalent and more likely to be exploited, while five detection tools disagree substantially.

The study compares five publicly available ReDoS detection tools and one regex correction tool across three datasets. An empirical analysis of all ReDoS vulnerabilities reported to the NVD finds they are becoming more prevalent and are much more likely to be exploited than non-ReDoS weaknesses. The detection tools exhibited substantial disagreement on whether a given regex is vulnerable.

arXiv cs.CR·Sep 9, 15:09 UTC · 6d agoResearch

Toward an Empirical Probabilistic Risk Manifestation Model of Organizational Cybersecurity in SMEs

Empirical study of 22 SME security assessments builds a probabilistic risk model and shows assessments can be cut 24-45% while retaining most critical findings.

Researchers analyzed 281 validated security findings from 22 real-world SME cybersecurity assessments conducted over two years via a pro bono university clinic. They derived an empirical Risk Manifestation Model linking eight organizational security functions to two exposure conditions, five attack mechanisms, and six outcome categories, using probability propagation to identify dominant risk pathways. The dominant pathway runs from asset exposure to credential compromise to unauthorized access, stable under leave-one-organization-out analysis. Retaining six functions reduces assessment burden by 24% while preserving 97% of critical findings; five functions cut burden 45% while preserving 89% of critical findings.

arXiv cs.CR·Sep 14, 01:15 UTC · 2d agoResearch

Mythos Vulnerability Firehose Hits a Human Bottleneck

Analysis of Project Glasswing findings shows only a fraction of discovered vulnerabilities have reached disclosure and even fewer are fixed.

Dark Reading reports that an analysis of Project Glasswing findings shows only a fraction of the vulnerabilities discovered by the program have reached disclosure, and an even smaller number have been fixed. The article examines how the volume of findings from the discovery program is bottlenecked by limited human triage and remediation capacity. The piece highlights growing tension between high-volume vulnerability discovery and the industry's ability to process, disclose and patch reports.

Dark Reading·Sep 9, 21:19 UTC · 6d agoResearch

Quantifying IIoT Sensor Node Criticality by Fusing its Data Criticality and Security Vulnerability

Researchers propose a Dempster–Shafer framework fusing IIoT sensor data criticality with CVSS 4.0/3.1 vulnerability scores to rank node criticality.

The paper introduces a framework that evaluates Industrial IoT sensor node criticality by fusing data criticality and cybersecurity vulnerability scores using Dempster–Shafer (D-S) theory. It was validated on a dataset from red wine production and is claimed to generalize to other industrial settings with minimal modification. Results show criticality rankings derived from CVSS 4.0 scores differ significantly from those derived from CVSS 3.1, underscoring how vulnerability scoring methodology affects security prioritization.

arXiv cs.CR·Sep 9, 07:03 UTC · 7d agoResearch

Propagation Model for SSC attacks: Why SBOM (tools) don't tell the whole truth

Study shows open-source SBOM tools only cover structural exposure and vulnerability presence, missing code reachability and taint-path analysis stages.

An arXiv paper proposes a four-stage propagation model for software supply chain attack effects and empirically evaluates four open-source SBOM tools against it using three projects and the Log4j vulnerability as the test case. Current SBOM tools systematically support only Stage 1 (structural exposure) and Stage 2 (vulnerability class presence), while Stage 3 (code reachability) and Stage 4 (taint path analysis) require capabilities absent from the SBOM ecosystem. The authors argue propagation-centred SSC security research is needed to prevent cyber risk from evolving into systemic risk.

arXiv cs.CR·Sep 4, 17:31 UTC · 11d agoResearch1

Enterprise Applications Carry 4.31x More Critical and High Vulnerabilities

Sonatype reports enterprise applications contain 4.31x more critical and high-severity vulnerabilities as accelerated software creation drives rising vulnerability levels.

Sonatype's analysis found enterprise applications carry 4.31 times more critical and high-severity vulnerabilities. The report links rising vulnerability levels to accelerated enterprise software creation. The findings are part of Sonatype's software supply chain research coverage reported by Infosecurity Magazine.

Infosecurity Magazine·Aug 18, 15:00 UTC · 28d agoIndustry

CISA: Most exploited vulnerabilities should have been eradicated decades ago

CISA says most exploited vulnerabilities are decades-old flaws, blaming organizational culture and weak Secure by Design adoption.

CISA assesses that the vulnerabilities most exploited in the wild are old flaws that should have been eradicated decades ago. The agency attributed the problem to organizational culture and systemic gaps in Secure by Design adoption. The Register's coverage frames the remarks as renewed pressure on vendors and operators to eliminate long-standing weaknesses.

The Register · Security·Aug 28, 11:29 UTC · 18d agoPolicy & legal in the wild

Evaluating the NIST Bugs Framework Against CWE as a Successor for Automated Vulnerability Classification

NIST Bugs Framework evaluation shows it is more structured and automation-friendly than CWE for automated vulnerability classification, with gaps in attribute guidance.

The paper evaluates NIST SP 800-231's Bugs Framework (BF) against CWE as a target for automated CVE classification using a systematically screened corpus of CVE-to-CWE research. An inter-rater study with 2 subject-matter experts mapping 13 CVEs showed strong agreement on BF's cause and operation axes but only fair agreement on the attribute axis. Automated classification was tested across two LLM deployments under different budgets, and findings support BF as more structured and automation-friendly than CWE, though gaps include under-specified attribute guidance and missing fix commits for closed-source software.

arXiv cs.CR·Sep 14, 23:18 UTC · 1d agoResearch1

Your Critical Vulnerabilities Might Not Be Your Biggest Risk

Autonomous penetration testing advocates prioritize exploitable attack paths over raw vulnerability severity for continuous security validation.

The article argues that scanner severity scores lack context: a critical flaw behind strong segmentation may be low priority, while a medium flaw on internet-facing systems can provide a foothold chained toward sensitive data. It positions autonomous penetration testing and attack path validation as the execution layer for continuous security validation, replacing point-in-time assessments. The piece is vendor-authored thought leadership rather than incident or vulnerability news.

The Hacker News·Sep 11, 11:30 UTC · 4d agoIndustry1

SEMA-GUARD: Semantic and Graph-Based Vulnerability Detection in Assembly Code

SEMA-GUARD uses semantic analysis and graph neural networks to detect vulnerabilities in assembly code, achieving 85.1% accuracy on a Juliet-derived benchmark.

SEMA-GUARD is a framework that detects vulnerabilities in compiled programs when source code is unavailable, targeting malware, firmware, and embedded systems analysis. It enriches control flow graphs with low-level execution semantics including stack manipulations, memory accesses, and data flow. Evaluated on a Juliet Test Suite set compiled to assembly and split into function-level chunks, it achieves 85.1% accuracy and an F1 score of 0.801, outperforming purely statistical or structural approaches.

arXiv cs.CR·Sep 15, 14:35 UTC · 20h agoResearch1

Vulnerability Localization Benchmark: Measuring Agentic Security Analysis at Repository Scale

VLoc Bench tests 27 language models at locating vulnerable files in 290 repositories; best system reaches 0.229 File F1 and 38.4% of tasks unsolved.

The Vulnerability Localization Benchmark (VLoc Bench) contains 500 real-world vulnerabilities from 290 repositories across six package ecosystems and 147 CWE categories, pairing pre-fix and post-fix repository snapshots. Agents receive only a CWE description and read-only terminal access to identify affected files, and must confirm absence on patched snapshots. The strongest of 27 language models and four static-analysis tools achieves just 0.229 File F1; 38.4% of tasks receive no correct localization, and effective localizers still report unsupported locations on patched repositories.

arXiv cs.AI / cs.LG / cs.CL·Sep 14, 17:44 UTC · 1d agoAI research

Frontier AI: Vulnerability Management's Systemic Revolution

Opinion: frontier AI like Anthropic's Mythos finds and exploits vulnerabilities at machine speed, forcing vulnerability and patch management programs to overhaul prioritization.

The author argues frontier AI models, exemplified by Anthropic's Mythos, can discover zero-days and chain exploits fast enough to overwhelm traditional vulnerability management. The piece recommends moving beyond CVSS, EPSS and KEV toward exposure management (CTEM) and automated, ring-based patch deployment. It also flags hard trade-offs between patching velocity and uptime requirements that organizations must resolve proactively.

The Hacker News·Aug 25, 11:14 UTC · 21d agoIndustry

Towards Scalable and Cost-Efficient Vulnerability Detection: A Study on Automatic Query Generation

A study finds LLM-synthesized CodeQL queries improve average F1-score by 82% over baseline queries, offering scalable vulnerability detection versus direct LLM scanning.

Researchers conducted an empirical study evaluating whether LLMs can synthesize executable CodeQL queries from National Vulnerability Database vulnerability data. LLM-generated queries significantly enhanced baseline CodeQL suites, yielding an 82% improvement in average F1-score across a diverse set of real-world vulnerabilities. A cost-benefit analysis shows direct LLM-based scanning of entire repositories is often computationally and financially prohibitive, while LLM query synthesis offers a scalable and cost-effective alternative for large-scale vulnerability detection.

arXiv cs.CR·Sep 9, 16:31 UTC · 6d agoResearch1

AI's Vulnerability Surge May Be More Manageable Than First Feared

New research argues the coming surge of vulnerabilities will be manageable for enterprise security teams that adopt the right triage and prioritization strategies.

A Dark Reading write-up of new research suggests the anticipated explosion in vulnerability volume may be less overwhelming than feared. The analysis indicates enterprise security teams can cope if they apply appropriate strategies for handling vulnerability influx. The piece is framed as guidance rather than a disclosure of specific flaws or incidents.

Dark Reading·Sep 2, 21:14 UTC · 13d agoResearch

Measuring the Security of the Evolving Software Supply Chain: a Research Agenda

Researchers propose a unified cross-ecosystem measurement agenda for software supply chain security, targeting dependency modeling and AI-generated dependency patterns.

The paper argues that existing quantitative measurement and vulnerability management approaches for software supply chain security are fragmented and ecosystem-specific, limiting comparable risk assessments. It lays out a research agenda starting with a Systematization of Knowledge to expose gaps in dependency modeling, transitive dependency treatment, and real-world exploitability of vulnerabilities. It further warns that AI-assisted development with coding LLMs will create dependency patterns not captured by traditional Software Composition Analysis tools, motivating a rethink of dependency modeling.

arXiv cs.CR·Sep 8, 14:37 UTC · 7d agoResearch

An Empirical Security Analysis of Open-Source Software Used in Onboard Satellite Systems

Study of 126 onboard satellite OSS repositories finds 2,827 security findings, 72% medium severity or higher, dominated by memory safety and code quality weaknesses.

Researchers performed an empirical security analysis of 126 public repositories of open-source software used in onboard satellite systems using SBOM generation, software composition analysis, static application security testing, infrastructure-as-code analysis, and secret scanning. After cleaning and deduplication the pipeline produced 2,827 findings, with medium-severity findings accounting for 49% and 72% classified medium or higher. A CWE-based taxonomy mapped all findings to eight weakness families, with Memory Safety and Code Quality dominating, followed by Input Validation and Injection. Project-developed code accounted for 81.4% of findings, though external dependency code remained relevant; findings do not establish mission-specific exploitability.

arXiv cs.CR·Sep 14, 11:54 UTC · 1d agoResearch1

CISA review makes the case for eliminating vulnerability classes

CISA's FY2024-2025 vulnerability review urges eliminating recurring vulnerability classes, finding 41.5% of 2025 KEV entries map to persistent 'stubborn weaknesses'.

CISA's Vulnerability Review for fiscal years 2024 and 2025 found most compromises stemmed from opportunistic exploitation of known, exposed vulnerabilities rather than nation-state zero-days or advanced tradecraft. The review found 41.5% of 2025 KEV catalog entries map to 'stubborn weaknesses' - injection flaws, improper input validation, memory-safety failures, path traversal and broken access control - recurring on the CWE Top 25 since 2019. CISA advocates Secure by Design practices, vulnerability class elimination, and buyer-driven 'Secure by Demand' contract requirements, while warning that AI-enabled vulnerability discovery will soon accelerate exploitation.

Help Net Security·Sep 1, 00:00 UTC · 15d agoPolicy & legal

AI vulnerability discovery scores the highest impact of 20 emerging risks

Gartner survey of 316 organizations ranks AI-driven vulnerability discovery as the top emerging risk, with tangible impact expected within roughly two years.

Gartner's quarterly survey had 316 risk managers, auditors, and senior executives rank 20 emerging threats in April and May, with AI discovery of cyber vulnerabilities ranked first, up from outside the top five the prior quarter. Respondents scored the impact time frame at 1.92 on a scale where 1 means under a year and 2 means one to two years, and 76% placed it in their top ten, ranking first in all four regions and highest among banking and financial respondents at 78%. The analysis notes AI now finds unknown flaws at volumes patching teams cannot absorb and that exploit development time has collapsed, citing defensive efforts like Anthropic's Project Glasswing and OpenAI's Daybreak. Gartner recommends recalibrating cyber risk impact, revisiting risk appetite, demanding stronger vendor security validation, and moving toward faster automated remediation.

Help Net Security·Aug 26, 00:00 UTC · 21d agoIndustry

Critical Langflow Vulnerability Exploited as Attacks on AI Platform Rise

Attacks exploiting CVE-2026-0768, a critical vulnerability in the Langflow low-code AI platform, are rising amid growing adversary attention this year.

CVE-2026-0768 is a critical vulnerability in Langflow, a low-code AI development platform, with exploitation attacks now rising. Dark Reading notes the platform has drawn increasing adversary attention in 2026. Organizations running exposed Langflow instances face elevated risk and should patch promptly and review instances for compromise.

Dark Reading·Sep 1, 20:48 UTC · 14d agoExploit / PoC in the wildCVE-2026-07681

Drowning in CVEs and thirsty for answers? Try CTEM

Sponsored Register piece argues traditional vulnerability management cannot scale with CVE volume and promotes Continuous Threat Exposure Management via Horizon3's NodeZero.

The sponsored article cites surging CVE volumes, CVSS triage shortcomings, NVD backlog, and AI-driven discovery accelerating an asymmetric vulnerability cycle. It outlines Gartner's five CTEM steps - scoping, discovery, prioritization, validation, and mobilization - and describes how Horizon3's NodeZero automated pentesting validates exploitable attack paths with evidence. Horizon3 says NodeZero uses a deterministic machine learning expert system rather than general LLMs, limiting generative AI to scoped tasks via AWS Bedrock.

The Register · Security·Sep 3, 15:00 UTC · 12d agoIndustry

NATO and an AI startup can now name and track software vulnerabilities

CyberScoop·Aug 10, 19:50 UTC · Aug 10, 2026Vulnerability in the wild

AI Is Ending the Era of Hidden Vulnerabilities — Are Vendors Ready?

Dark Reading argues AI-assisted bug discovery is flooding vendors with vulnerability reports, straining disclosure processes and secure-by-design commitments.

The Dark Reading analysis describes a surge of bug reports driven by AI-powered discovery, exposing bottlenecks in vendor triage and disclosure pipelines. It argues this volume is revealing secure-by-design failures and questions whether vendors can keep pace with the rising tide of findings.

Dark Reading·Sep 4, 13:00 UTC · 11d agoIndustry

The Vulnpocalypse Is Repricing the Bug Bounty Economy

Surging AI-generated vulnerability reports are driving down bug bounty payouts, threatening the economics of independent security researchers.

Dark Reading argues that a surge of AI-powered vulnerability reports is repricing the bug bounty economy. As programs absorb escalating report volume, payouts for many classes of findings are falling. The trend could undermine the livelihoods of independent full-time bug bounty researchers.

Dark Reading·Aug 28, 13:00 UTC · 18d agoIndustry

Securing the unpatchable in an age of AI-driven vulnerabilities

Cisco Talos argues AI-driven vulnerability discovery leaves unpatchable OT systems exposed, recommending virtual patching via NGFW/IPS and micro-segmentation.

AI-assisted code analysis is uncovering vulnerabilities faster than organizations can patch, leaving certified or end-of-life OT systems with unmitigated known flaws. Talos recommends virtual patching with next-generation firewalls and IPS, micro-segmentation using VLANs and ACLs, and building visibility-based inventories of legacy systems. The article cites WannaCry's impact on the NHS and 2023 exploitation of end-of-life software in government systems, and warns that air gaps and data diodes are routinely circumvented by operational shortcuts.

Cisco Talos·10:00 UTC · 1h agoResearch