# CVE fatigue

CVE fatigue is the condition in which developers and IT professionals become overwhelmed by the constant influx of software vulnerability alerts and remediation demands.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Navigating Vulnerability Hysteria in the AI Era

DevFeed: [Navigating Vulnerability Hysteria in the AI Era](<https://devfeed.tech/articles/navigating-vulnerability-hysteria-in-the-ai-era-144347.md>)

Original publisher: [Read original article](<https://www.darkreading.com/vulnerabilities-threats/navigating-vulnerability-hysteria-ai-era>)

Author: Fahmida Y Rashid

Published: 2026-11-19T19:46:44Z

Content type: article

Language: en

Sources: [Cyber Newsroom](<https://devfeed.tech/sources/cyber-newsroom.md>)

Topics: [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [Cybersecurity](<https://devfeed.tech/topics/cybersecurity.md>), [Exploit](<https://devfeed.tech/topics/exploit.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [cybersecurity and infrastructure security agency](<https://devfeed.tech/topics/cybersecurity-and-infrastructure-security-agency.md>), [X (Twitter)](<https://devfeed.tech/topics/twitter.md>)

Tags: [age-of-ai](<https://devfeed.tech/tags/age-of-ai.md>), [ai](<https://devfeed.tech/tags/ai.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-109618](<https://devfeed.tech/tags/cve-2026-109618.md>), [cve-2026-109619](<https://devfeed.tech/tags/cve-2026-109619.md>), [cve-2026-114938](<https://devfeed.tech/tags/cve-2026-114938.md>), [cve-2026-123007](<https://devfeed.tech/tags/cve-2026-123007.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [disclosures](<https://devfeed.tech/tags/disclosures.md>), [hysteria](<https://devfeed.tech/tags/hysteria.md>), [patch](<https://devfeed.tech/tags/patch.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

The PHP2Shell disclosures prompted organizations to take websites and services offline amid fears that AI could speed attacks, but the expected immediate wave of exploitation did not appear during "Black October." The article cautions that high severity and AI-assisted discovery do not guarantee quick compromise: exploit paths can be complex, proofs of concept flawed, and application behavior can matter. Java4Shell, for example, has no universal exploit and requires application-dependent steps. Repeated emergency shutdowns can cost time, money, and productivity and may lead teams to ignore future warnings; some operations cannot safely go offline. The reporters recommend risk-based prioritization, knowing what systems and suppliers use, maintaining security fundamentals, and preparing to respond. They say CISOs should clearly communicate technical and operational risks so executive or operational leaders can weigh them and make shutdown decisions.

### Source excerpt

Navigating Vulnerability Hysteria in the AI Era The pressure on cybersecurity teams to patch critical vulnerabilities is reaching a boiling point, exacerbated by incessant coverage and rapid-fire disclosures of AI-discovered bugs. Last month, it wa ... Read more Published Date: Nov 19, 2026 (1 hour, 41 minutes ago) Vulnerabilities has been mentioned in this article. CVE-2026-123007 CVE-2026-114938 CVE-2026-109619 CVE-2026-109618

## The death of the 14-day patch: Surviving machine-speed vulnerability discovery

DevFeed: [The death of the 14-day patch: Surviving machine-speed vulnerability discovery](<https://devfeed.tech/articles/the-death-of-the-14-day-patch-surviving-machine-speed-vulnerability-discovery-130470.md>)

Original publisher: [Read original article](<https://thenewstack.io/machine-speed-vulnerability-discovery/>)

Author: Ory Team

Published: 2026-11-12T15:00:00Z

Content type: opinion

Language: en

Sources: [The New Stack](<https://devfeed.tech/sources/the-new-stack.md>)

Topics: [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>), [AI in cybersecurity](<https://devfeed.tech/topics/ai-in-cybersecurity.md>), [Managed Services](<https://devfeed.tech/topics/managed-services.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [software composition analysis](<https://devfeed.tech/topics/software-composition-analysis.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-security](<https://devfeed.tech/tags/agentic-security.md>), [agents](<https://devfeed.tech/tags/agents.md>), [api](<https://devfeed.tech/tags/api.md>), [api-gateway](<https://devfeed.tech/tags/api-gateway.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [architectures](<https://devfeed.tech/tags/architectures.md>), [argo](<https://devfeed.tech/tags/argo.md>), [argo-rollouts](<https://devfeed.tech/tags/argo-rollouts.md>), [argocd](<https://devfeed.tech/tags/argocd.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [automate](<https://devfeed.tech/tags/automate.md>), [automation](<https://devfeed.tech/tags/automation.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [canary](<https://devfeed.tech/tags/canary.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cilium](<https://devfeed.tech/tags/cilium.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [devops](<https://devfeed.tech/tags/devops.md>), [ory](<https://devfeed.tech/tags/ory.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [post-contributed](<https://devfeed.tech/tags/post-contributed.md>), [security](<https://devfeed.tech/tags/security.md>), [sponsor-ory](<https://devfeed.tech/tags/sponsor-ory.md>), [sponsored-post-contributed](<https://devfeed.tech/tags/sponsored-post-contributed.md>), [vulnerability-discovery](<https://devfeed.tech/tags/vulnerability-discovery.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

The article argues that automated vulnerability discovery has made the traditional two-week patch cycle unsustainable. It attributes the surge to agentic systems that traverse code and dependencies, test exploits, and focus on foundational infrastructure, creating triage backlogs, exposure windows, and pressure on development and compliance teams. It recommends shifting patch work upstream for critical components: use managed services for edge and identity layers, or commercial open-source subscriptions with contractual remediation SLAs and long-term backports where SaaS is unsuitable. For internally maintained services, it proposes automated GitOps updates, progressive deployments, and eBPF runtime shielding to help verify patches and contain risk during rollout. The text frames automation and outsourced maintenance as ways to reduce emergency patching burdens.

### Source excerpt

For decades, enterprise vulnerability management ran on human time: A security researcher manually dissected a binary, traced execution paths, built The post The death of the 14-day patch: Surviving machine-speed vulnerability discovery appeared first on The New Stack.

## The 13-Hour Collapse: Why Frontier AI Demands the End of Periodic Patching

DevFeed: [The 13-Hour Collapse: Why Frontier AI Demands the End of Periodic Patching](<https://devfeed.tech/articles/the-13-hour-collapse-why-frontier-ai-demands-the-end-of-periodic-patching-105702.md>)

Original publisher: [Read original article](<https://blogs.vmware.com/tanzu/the-13-hour-collapse-why-frontier-ai-demands-the-end-of-periodic-patching/>)

Author: darin zook and cote

Published: 2026-10-28T23:49:17Z

Content type: article

Language: en

Sources: [VMware](<https://devfeed.tech/sources/vmware-blogs.md>)

Topics: [internal developer platform automation](<https://devfeed.tech/topics/internal-developer-platform-automation.md>), [Frontier AI](<https://devfeed.tech/topics/frontier-ai.md>), [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>), [open source maintenance](<https://devfeed.tech/topics/open-source-maintenance.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [container native](<https://devfeed.tech/topics/container-native.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-sdlc](<https://devfeed.tech/tags/agentic-sdlc.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding-assistants](<https://devfeed.tech/tags/ai-coding-assistants.md>), [ai-model](<https://devfeed.tech/tags/ai-model.md>), [ai-security](<https://devfeed.tech/tags/ai-security.md>), [alert-fatigue](<https://devfeed.tech/tags/alert-fatigue.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [artifacts](<https://devfeed.tech/tags/artifacts.md>), [attack](<https://devfeed.tech/tags/attack.md>), [automated](<https://devfeed.tech/tags/automated.md>), [continuous](<https://devfeed.tech/tags/continuous.md>), [frontier](<https://devfeed.tech/tags/frontier.md>), [frontier-ai](<https://devfeed.tech/tags/frontier-ai.md>), [modern-apps](<https://devfeed.tech/tags/modern-apps.md>), [patching](<https://devfeed.tech/tags/patching.md>), [platform](<https://devfeed.tech/tags/platform.md>), [security](<https://devfeed.tech/tags/security.md>), [tanzu-platform](<https://devfeed.tech/tags/tanzu-platform.md>), [vmware](<https://devfeed.tech/tags/vmware.md>)

### AI overview

The article argues that vulnerability response must move from monthly, ticket driven patching to a continuous platform control loop, citing exploit weaponization within 24 hours and a reported 13 hours for LMDeploy. It proposes combining TrueSource by Broadcom's clean room SLSA Level 3 builds, signatures, attestations and SBOMs with VMware Tanzu Platform. Tanzu Buildpacks separate application code from runtimes and the root OS, allowing administrators to update a buildpack and restage applications fleet wide without source edits; Stacks and Stemcells address lower layers. The described loop also uses BOSH to repave VMs, CredHub to rotate credentials, and Tanzu Hub to rescore CVEs using exposure context and verify patched state. The article contrasts this with DIY environments where teams rebuild images and coordinate developer and operations handoffs. These mechanisms and benefits are presented as vendor claims; the supplied text does not independently validate them.

### Source excerpt

To survive the era of Frontier AI, patching can no longer be an ad-hoc calendar event. It must become a continuous, automated platform response. Organizations must shift to a continuous platform control loop. By adopting a pre-engineered architecture, the undifferentiated heavy lifting of staying secure is built-in natively, rather than built by you. The post ... Continued The post The 13-Hour Collapse: Why Frontier AI Demands the End of Periodic Patching appeared first on VMware Blogs.

## Defenders need more time to patch with the influx of patching hitting operations

DevFeed: [Defenders need more time to patch with the influx of patching hitting operations](<https://devfeed.tech/articles/defenders-need-more-time-to-patch-with-the-influx-of-patching-hitting-operations-105418.md>)

Original publisher: [Read original article](<https://blogs.cisco.com/security/defenders-need-more-time-to-patch-with-the-influx-of-patching-hitting-operations/>)

Author: Jason Maynard

Published: 2026-10-28T15:00:14Z

Content type: article

Language: en

Sources: [Security @ Cisco](<https://devfeed.tech/sources/security-cisco-blogs.md>)

Topics: [Cisco Secure Networking](<https://devfeed.tech/topics/cisco-secure-networking.md>), [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>), [Nexus Dashboard](<https://devfeed.tech/topics/nexus-dashboard.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-cybersecurity](<https://devfeed.tech/tags/ai-cybersecurity.md>), [cisco](<https://devfeed.tech/tags/cisco.md>), [cisco-live-protect](<https://devfeed.tech/tags/cisco-live-protect.md>), [cisco-talos](<https://devfeed.tech/tags/cisco-talos.md>), [containers](<https://devfeed.tech/tags/containers.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [days](<https://devfeed.tech/tags/days.md>), [live-protect](<https://devfeed.tech/tags/live-protect.md>), [need](<https://devfeed.tech/tags/need.md>), [network-security](<https://devfeed.tech/tags/network-security.md>), [operations](<https://devfeed.tech/tags/operations.md>), [patch](<https://devfeed.tech/tags/patch.md>), [patches](<https://devfeed.tech/tags/patches.md>), [patching](<https://devfeed.tech/tags/patching.md>), [reduce](<https://devfeed.tech/tags/reduce.md>), [security](<https://devfeed.tech/tags/security.md>), [time](<https://devfeed.tech/tags/time.md>), [time-to-patch](<https://devfeed.tech/tags/time-to-patch.md>), [virtual-patching](<https://devfeed.tech/tags/virtual-patching.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

The excerpt describes Cisco's compensating controls as ways to reduce exposure while organizations work through patching, which it says can take up to 43 days. Network virtual patching uses Talos Snort rules on Secure Firewall to log or drop matching exploit traffic; Secure Workload inventory and Firepower Recommendations can narrow signatures to relevant hosts. This can cover many systems before a vendor binary patch is available, but it sees only traffic through the firewall, signatures may miss novel variants, and the vulnerable software remains installed. Live Protect instead applies a temporary, Cisco-validated eBPF policy on supported Cisco infrastructure, starting with Nexus 9000 NX-OS: deploy in monitor mode, move to enforcement, then remove it after installing the permanent image. The excerpt says it requires no image upgrade or reboot and can address some local or control-plane issues that do not appear as network traffic. It presents workload and runtime protections as complementary controls. None replaces installing the actual patch.

### Source excerpt

Discover how Cisco Live Protect, virtual patching, and Secure Workload help defenders reduce vulnerability exposure while buying time for critical patches.

## Defenders need more time to patch with the influx of patching hitting operations

DevFeed: [Defenders need more time to patch with the influx of patching hitting operations](<https://devfeed.tech/articles/defenders-need-more-time-to-patch-with-the-influx-of-patching-hitting-operations-104752.md>)

Original publisher: [Read original article](<https://blogs.cisco.com/security/defenders-need-more-time-to-patch-with-the-influx-of-patching-hitting-operations>)

Author: Jason Maynard

Published: 2026-10-28T15:00:14Z

Content type: article

Language: en

Sources: [Cisco Blogs](<https://devfeed.tech/sources/cisco-blogs.md>)

Topics: [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>), [Cisco Secure Networking](<https://devfeed.tech/topics/cisco-secure-networking.md>), [aws inspector](<https://devfeed.tech/topics/aws-inspector.md>)

Tags: [ai-cybersecurity](<https://devfeed.tech/tags/ai-cybersecurity.md>), [cisco](<https://devfeed.tech/tags/cisco.md>), [cisco-live-protect](<https://devfeed.tech/tags/cisco-live-protect.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [days](<https://devfeed.tech/tags/days.md>), [defense-in-depth](<https://devfeed.tech/tags/defense-in-depth.md>), [ebpf](<https://devfeed.tech/tags/ebpf.md>), [live-protect](<https://devfeed.tech/tags/live-protect.md>), [network-security](<https://devfeed.tech/tags/network-security.md>), [patching](<https://devfeed.tech/tags/patching.md>), [security](<https://devfeed.tech/tags/security.md>), [time](<https://devfeed.tech/tags/time.md>), [time-to-patch](<https://devfeed.tech/tags/time-to-patch.md>), [virtual-patching](<https://devfeed.tech/tags/virtual-patching.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

The article says Cisco's compensating controls can reduce exposure while organizations work through patching, which it says can take up to 43 days; none replaces the actual patch. Virtual patching uses Talos Snort rules on Secure Firewall to inspect and log or drop matching traffic, optionally narrowed to relevant hosts using Secure Workload inventory and FMC recommendations. It can cover many hosts and apply to third-party software or OT when traffic passes an inspection point, but misses traffic outside that point, may miss novel variants, and leaves the vulnerable software on disk. Live Protect is a temporary, Cisco-validated eBPF runtime shield for supported Cisco infrastructure, starting with Nexus 9000 NX-OS: deploy in monitor mode, move to enforcement, then remove it after installing the permanent image. It requires no image upgrade or reboot and can address some local or control-plane issues that network traffic signatures do not see; the article does not present it as a patch. Secure Workload and Isovalent runtime protections are described as additional workload-level controls.

### Source excerpt

Discover how Cisco Live Protect, virtual patching, and Secure Workload help defenders reduce vulnerability exposure while buying time for critical patches.

## The Impact of AI on CVEs: Industry Challenges

DevFeed: [The Impact of AI on CVEs: Industry Challenges](<https://devfeed.tech/articles/the-impact-of-ai-on-cves-industry-challenges-105752.md>)

Original publisher: [Read original article](<https://jfrog.com/blog/the-impact-of-ai-on-cves-industry-challenges/>)

Author: drewt@jfrog.com

Published: 2026-10-27T14:00:05Z

Content type: article

Language: en

Sources: [From the Frog's mouth - JFrog Blog](<https://devfeed.tech/sources/from-the-frog-s-mouth-jfrog-blog.md>)

Topics: [vulnerability-research](<https://devfeed.tech/topics/vulnerability-research.md>), [Security research](<https://devfeed.tech/topics/security-research.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Generative AI](<https://devfeed.tech/topics/generative-ai.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>), [NVD](<https://devfeed.tech/topics/nvd.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>)

Tags: [2021](<https://devfeed.tech/tags/2021.md>), [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-ml](<https://devfeed.tech/tags/ai-ml.md>), [application-security](<https://devfeed.tech/tags/application-security.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [common-vulnerabilities-and-exposures](<https://devfeed.tech/tags/common-vulnerabilities-and-exposures.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cves](<https://devfeed.tech/tags/cves.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [devsecops](<https://devfeed.tech/tags/devsecops.md>), [disclosure](<https://devfeed.tech/tags/disclosure.md>), [generative](<https://devfeed.tech/tags/generative.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [impact](<https://devfeed.tech/tags/impact.md>), [industry](<https://devfeed.tech/tags/industry.md>), [nvd](<https://devfeed.tech/tags/nvd.md>), [open-source-security](<https://devfeed.tech/tags/open-source-security.md>), [research](<https://devfeed.tech/tags/research.md>), [security](<https://devfeed.tech/tags/security.md>), [security-research](<https://devfeed.tech/tags/security-research.md>), [software-supply-chain-security](<https://devfeed.tech/tags/software-supply-chain-security.md>), [volume](<https://devfeed.tech/tags/volume.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [vulnerability-research](<https://devfeed.tech/tags/vulnerability-research.md>)

### AI overview

AI has increased both the pace of vulnerability discovery and the volume of reports teams must verify, prioritize, and fix. The article cites curl's decision to end its bug bounty after fewer than 5% of submissions were confirmed as vulnerabilities, GNOME's shorter disclosure window, and NIST's prioritization of exploited and critical CVEs while moving older backlogged items to "Not Scheduled." It describes fabricated SQLite advisories with nonexistent functions and impossible line numbers, as well as severity disagreements over libcurl flaws that maintainers rated Low to Medium and CISA rated mostly High or Critical. AI can also help turn disclosures into exploits, while maintainers and organizations still need time to validate reports, prepare fixes, test updates, and deploy patches. The article argues that CVSS Base scores alone do not establish risk and that growing queues strain both verification and remediation.

### Source excerpt

Integrating artificial intelligence into cybersecurity has fundamentally changed vulnerability research - and not necessarily for the better. For decades, discovering and verifying Common Vulnerabilities and Exposures (CVEs) required deep technical expertise, creating a disciplined process that kept disclosure volume relatively manageable. Today, Generative AI has obliterated that barrier to entry. While AI empowers seasoned security ...

## How AI Fuels the Web Security Goldrush

DevFeed: [How AI Fuels the Web Security Goldrush](<https://devfeed.tech/articles/how-ai-fuels-the-web-security-goldrush-99144.md>)

Original publisher: [Read original article](<https://speckyboy.com/how-ai-fuels-the-web-security-goldrush/>)

Author: Eric Karkovack

Published: 2026-10-25T11:39:45Z

Content type: article

Language: en

Sources: [Speckyboy Design Magazine](<https://devfeed.tech/sources/speckyboy-design-magazine.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [ai code review](<https://devfeed.tech/topics/ai-code-review.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>), [Web](<https://devfeed.tech/topics/web.md>)

Tags: [agencies](<https://devfeed.tech/tags/agencies.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [artificial-intelligence-ai](<https://devfeed.tech/tags/artificial-intelligence-ai.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [bounty](<https://devfeed.tech/tags/bounty.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [content-delivery-networks](<https://devfeed.tech/tags/content-delivery-networks.md>), [freelance-design](<https://devfeed.tech/tags/freelance-design.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [web-developers](<https://devfeed.tech/tags/web-developers.md>), [web-security](<https://devfeed.tech/tags/web-security.md>), [wordpress-ai](<https://devfeed.tech/tags/wordpress-ai.md>)

### AI overview

AI can help security researchers find vulnerable code patterns and connections that human reviewers may miss; the excerpt cites WordPress security fixes and the "Protect the Shire" initiative as examples. The same capabilities are available to malicious actors, while a surge in vulnerability reports can overwhelm developers and make it difficult to distinguish urgent, exploitable flaws from issues requiring unlikely attack steps. The article argues that freelancers and agencies cannot manage the volume alone: automated updates are fast but do not ensure safety or stability, and it calls for better ways to assess threats and apply patches quickly. It suggests hosts and CDNs such as Cloudflare could help deliver mitigation at scale. These are proposed directions, not detailed implementation guidance.

### Source excerpt

AI has quickly become a key tool for the modern web. Developers, web hosts, and site owners are adopting it to reduce costs, increase efficiency, and serve customers (we can... The post How AI Fuels the Web Security Goldrush appeared first on Speckyboy Design Magazine.

## The Vulnerability Apocalypse and Why We Should Fund Open Source

DevFeed: [The Vulnerability Apocalypse and Why We Should Fund Open Source](<https://devfeed.tech/articles/the-vulnerability-apocalypse-and-why-we-should-fund-open-source-98586.md>)

Original publisher: [Read original article](<https://www.eff.org/deeplinks/2026/10/vulnerability-apocalypse-and-why-we-should-fund-open-source>)

Author: Cooper Quintin

Published: 2026-10-23T22:36:46Z

Content type: opinion

Language: en

Sources: [Deeplinks](<https://devfeed.tech/sources/deeplinks.md>)

Topics: [open-source-security](<https://devfeed.tech/topics/open-source-security.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [open source maintenance](<https://devfeed.tech/topics/open-source-maintenance.md>), [NVD](<https://devfeed.tech/topics/nvd.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [common-vulnerabilities-and-exposures](<https://devfeed.tech/tags/common-vulnerabilities-and-exposures.md>), [interactive-websites](<https://devfeed.tech/tags/interactive-websites.md>), [nist](<https://devfeed.tech/tags/nist.md>), [nvd](<https://devfeed.tech/tags/nvd.md>), [october](<https://devfeed.tech/tags/october.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [open-source-maintenance](<https://devfeed.tech/tags/open-source-maintenance.md>), [open-source-projects](<https://devfeed.tech/tags/open-source-projects.md>), [php](<https://devfeed.tech/tags/php.md>), [powers](<https://devfeed.tech/tags/powers.md>), [programming-language](<https://devfeed.tech/tags/programming-language.md>), [security](<https://devfeed.tech/tags/security.md>), [security-vulnerabilities](<https://devfeed.tech/tags/security-vulnerabilities.md>), [software-security](<https://devfeed.tech/tags/software-security.md>), [software-vulnerabilities](<https://devfeed.tech/tags/software-vulnerabilities.md>), [technical-analysis](<https://devfeed.tech/tags/technical-analysis.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

The article argues that critical open-source projects need more funding and staff as AI makes vulnerability discovery easier and faster. It says researchers using recent models rediscovered two PHP vulnerabilities first identified in a 2024 audit, found ways to exploit them, and coordinated fixes with PHP maintainers. Leaks and an early patch release disrupted the planned disclosure; the article reports active exploitation and more than 33 million websites still running vulnerable PHP versions at the time of writing. It describes possible consequences including site takeover, data theft, malware, and denial-of-service attacks, and notes severe bugs also affected Node.js and GitLab. The excerpt attributes the resulting pressure to under-resourced volunteer maintainers and calls on corporations that depend on open-source software to support its upkeep. Technical vulnerability analysis is outside the post's stated scope.

### Source excerpt

If you use the internet at all, you may have noticed that a large percentage of sites suddenly went down earlier this week--and all your nerdiest friends were talking about "The Vulnerability Apocalypse" and this thing called PHP that powers nearly 70% of the websites on the internet. You may find yourself wondering: what is PHP, what just happened, what is the vulnerability apocalypse, and what do I need to do? To find out what you can personally do read the first blog post in this series! What Is PHP? PHP is a programming language used mainly to create interactive websites. Facebook, Wordpress, Wikipedia, Etsy, and other major sites all use or were originally built on PHP. It is a long-established mainstay of web development. But because it is open-source, maintenance of these critical systems depends on a small number of volunteers working on this in their free time. The disaster scenario that happened this past week is the perfect example of why we need more money and people supporting open-source projects. Corporations should be contributing both. What Is the Vulnerability Apocalypse? Common Vulnerabilities and Exposures (CVEs) are the way that security professionals file reports about vulnerabilities in software. The National Vulnerability Database (NVD), run by NIST, is the official national database of CVEs. In other words, CVE reports managed by NIST are the closest thing we have to a canonical database of security vulnerabilities in software. The NVD currently has around 400,000 CVEs that have been filed and accepted since 1988. In just the month of October, 13,000 new CVEs have been submitted. This means that 3% of critical software security bugs that have ever been officially logged were found in the last month alone. And it's likely that by the end of the year over a quarter of the software vulnerabilities that have ever been found will be from 2026. Computer vulnerabilities reported are rising exponentially. Source: CVE Tracker This research is being dr

## Remediation in the era of AI: Fix what matters first

DevFeed: [Remediation in the era of AI: Fix what matters first](<https://devfeed.tech/articles/remediation-in-the-era-of-ai-fix-what-matters-first-93137.md>)

Original publisher: [Read original article](<https://www.computerworld.com/article/4238649/remediation-in-the-era-of-ai-fix-what-matters-first.html>)

Author: Anna Boulware

Published: 2026-10-21T18:45:47Z

Content type: article

Language: en

Sources: [Computerworld](<https://devfeed.tech/sources/computerworld.md>)

Topics: [Exposure Management](<https://devfeed.tech/topics/exposure-management.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>)

Tags: [actively-exploited](<https://devfeed.tech/tags/actively-exploited.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [applications](<https://devfeed.tech/tags/applications.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-risk-management](<https://devfeed.tech/tags/artificial-intelligence-risk-management.md>), [backlog](<https://devfeed.tech/tags/backlog.md>), [business](<https://devfeed.tech/tags/business.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [critical](<https://devfeed.tech/tags/critical.md>), [customer](<https://devfeed.tech/tags/customer.md>), [cve](<https://devfeed.tech/tags/cve.md>), [development](<https://devfeed.tech/tags/development.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [internet](<https://devfeed.tech/tags/internet.md>), [it](<https://devfeed.tech/tags/it.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [lateral](<https://devfeed.tech/tags/lateral.md>), [library](<https://devfeed.tech/tags/library.md>), [remediation](<https://devfeed.tech/tags/remediation.md>), [risk-management](<https://devfeed.tech/tags/risk-management.md>), [storytype-brandpost](<https://devfeed.tech/tags/storytype-brandpost.md>)

### AI overview

Prioritize reducing reachable, consequential exposures rather than chasing vulnerability counts. Combine active exploitation, attacker access paths, business impact, sensitive data, and compensating controls: the excerpt contrasts a critical flaw on an internal development server with a publicly exploitable high-rated flaw on a customer-facing server, and favors the latter. Replace periodic scan-and-ticket cycles with continuous monitoring of disclosures, configuration changes, and newly exposed assets, then verify fixes and retain audit-ready evidence. Automate routine endpoint updates and established configuration corrections with staged rollouts; use human judgment and scheduled windows for higher-impact production or network changes. Measure outcomes such as time to remediate actively exploited flaws and trends in internet-facing exposures, rather than patches or tickets closed. The stated goal is deliberate, continuous reduction of meaningful risk, not zero vulnerabilities.

### Source excerpt

Every IT and security team knows the feeling of opening a vulnerability report and seeing a number that only goes up. Thousands of findings. Hundreds marked critical. A backlog that grows faster than any team can close it. For years, the default response has been to work harder: more scans, more tickets, more overtime. But the volume of vulnerabilities, accelerated by AI-assisted discovery and a sprawling mix of endpoints, cloud services, and applications, has outpaced that approach. Shift from vulnerability counts to exposure reduction -> The question has shifted from, "How do we fix everything?" To, "What should we fix first, and why?" Vulnerabilities are not the same as exposures A vulnerability is a weakness in software or configuration. An exposure is a weakness that can realistically be reached and exploited in your environment, with consequences that matter. That difference is where remediation prioritization begins. A vulnerable library on a decommissioned server with no network access is technically a finding. It is not a meaningful exposure. A misconfigured remote access gateway facing the internet may never appear on a CVE list, yet it can represent serious risk. Focusing on exposure reduction, rather than raw vulnerability counts, helps teams spend limited time where it changes outcomes. Risk-based prioritization works best when it combines technical and business factors. Is the weakness being actively exploited? Can attackers reach the affected system from the internet or through common lateral paths? What business service does the system support, and what would disruption cost? Does it store or process sensitive data? Are compensating controls already reducing the risk? Consider two findings: a critical-rated flaw on an internal development server with no sensitive data, versus a high-rated flaw on a customer-facing web server with exploit code circulating publicly. On severity alone, the first wins. On actual risk, the second is the clear priority, as

## Cloudflare links vulnerability discovery to defense with OpenAI

DevFeed: [Cloudflare links vulnerability discovery to defense with OpenAI](<https://devfeed.tech/articles/cloudflare-links-vulnerability-discovery-to-defense-with-openai-94016.md>)

Original publisher: [Read original article](<https://openai.com/index/cloudflare-cyber>)

Published: 2026-10-21T00:00:00Z

Content type: article

Language: en

Sources: [OpenAI News](<https://devfeed.tech/sources/openai-news.md>)

Topics: [Cloudflare](<https://devfeed.tech/topics/cloudflare.md>), [OpenAI](<https://devfeed.tech/topics/openai.md>), [codex](<https://devfeed.tech/topics/codex.md>), [ai code review](<https://devfeed.tech/topics/ai-code-review.md>), [software security audit](<https://devfeed.tech/topics/software-security-audit.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [actions](<https://devfeed.tech/tags/actions.md>), [ai](<https://devfeed.tech/tags/ai.md>), [build](<https://devfeed.tech/tags/build.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [code](<https://devfeed.tech/tags/code.md>), [code-quality](<https://devfeed.tech/tags/code-quality.md>), [codex](<https://devfeed.tech/tags/codex.md>), [defense](<https://devfeed.tech/tags/defense.md>), [developers](<https://devfeed.tech/tags/developers.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [links](<https://devfeed.tech/tags/links.md>), [openai](<https://devfeed.tech/tags/openai.md>), [quality](<https://devfeed.tech/tags/quality.md>), [review](<https://devfeed.tech/tags/review.md>), [uses](<https://devfeed.tech/tags/uses.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Cloudflare's early-access Vulnerability Discovery and Remediation service combines OpenAI models accessed through Daybreak with live traffic and security signals to investigate customer-authorized code, assess evidence, and prioritize potential vulnerabilities. It proposes code patches and, where appropriate, custom web application firewall rules; automated checks and Cloudflare team review precede sharing proposals with customers, who decide what to implement. Separately, Cloudflare says developers use Codex to increase output and improve code quality. In one cited rebuild, four developers completed and tested the work in three days for $1,100 in token spend; the estimate without Codex was months of sequencing and perhaps ten times more developers.

### Source excerpt

Cloudflare uses OpenAI Daybreak to investigate vulnerabilities and propose fixes for review. Its developers use Codex to build faster and improve code quality.

## There's only so much code: the rise in vulnerability numbers

DevFeed: [There's only so much code: the rise in vulnerability numbers](<https://devfeed.tech/articles/there-s-only-so-much-code-the-rise-in-vulnerability-numbers-90820.md>)

Original publisher: [Read original article](<https://blog.talosintelligence.com/theres-only-so-much-code-the-rise-in-vulnerability-numbers/>)

Author: Kri Dontje

Published: 2026-10-20T15:31:22Z

Content type: article

Language: en

Sources: [Cisco Talos Blog](<https://devfeed.tech/sources/cisco-talos-blog.md>)

Topics: [code security](<https://devfeed.tech/topics/code-security.md>), [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [Exploit](<https://devfeed.tech/topics/exploit.md>), [exploit chaining](<https://devfeed.tech/topics/exploit-chaining.md>), [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>), [CVE-2021-44228](<https://devfeed.tech/topics/cve-2021-44228.md>), [snyk-security-intel](<https://devfeed.tech/topics/snyk-security-intel.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-evaluation](<https://devfeed.tech/tags/ai-evaluation.md>), [ai-models](<https://devfeed.tech/tags/ai-models.md>), [anomaly-detection](<https://devfeed.tech/tags/anomaly-detection.md>), [attack](<https://devfeed.tech/tags/attack.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [automation](<https://devfeed.tech/tags/automation.md>), [backlog](<https://devfeed.tech/tags/backlog.md>), [behavioral-detection](<https://devfeed.tech/tags/behavioral-detection.md>), [blocking](<https://devfeed.tech/tags/blocking.md>), [bottlenecks](<https://devfeed.tech/tags/bottlenecks.md>), [bug](<https://devfeed.tech/tags/bug.md>), [code](<https://devfeed.tech/tags/code.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [microsoft-patch-tuesday](<https://devfeed.tech/tags/microsoft-patch-tuesday.md>), [on-the-radar](<https://devfeed.tech/tags/on-the-radar.md>), [patch](<https://devfeed.tech/tags/patch.md>), [patch-tuesday](<https://devfeed.tech/tags/patch-tuesday.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

AI-assisted scanning is surfacing vulnerabilities in the backlog of older, widely used code, driving a sharp rise in advisories and straining open-source maintainers and the traditional 90-day disclosure window. The increase has not translated proportionally into known exploitation: the excerpt reports 105% year-over-year growth in published CVEs versus 37% growth in known exploited vulnerabilities, and three in-the-wild exploits among September's 975 Microsoft advisories. The article says disclosure does not equal weaponization, while cautioning that AI may help attackers analyze patches faster. It recommends prioritizing flaws that offer viable paths into an organization's environment, upgrading and using interim mitigations such as LiveProtect, adding behavioral anomaly detection and defense in depth, and evaluating new code with current AI models. The author expects discovery rates may eventually level off as legacy code is remediated, but presents this as a possibility, not a certainty.

### Source excerpt

The September Microsoft Patch Tuesday release included 975 vulnerability advisories. This month, 1,415 vulnerabilities were just dropped. Compared to a pre-June average of 100 a month, that increase is staggering. Where did they come from? And what does the future look like?

## Oh Look, The Foot Gun Went Off Again (Citrix NetScaler PreAuth Command Injection CVE-2026-88771)

DevFeed: [Oh Look, The Foot Gun Went Off Again (Citrix NetScaler PreAuth Command Injection CVE-2026-88771)](<https://devfeed.tech/articles/oh-look-the-foot-gun-went-off-again-citrix-netscaler-preauth-command-injection-cve-2026-88771-61078.md>)

Original publisher: [Read original article](<https://labs.watchtowr.com/oh-look-the-foot-gun-went-off-again-citrix-netscaler-preauth-command-injection-cve-2026-88771/>)

Author: Sina Kheirkhah (@SinSinology)

Published: 2026-09-28T10:55:54Z

Content type: article

Language: en

Sources: [watchTowr Labs](<https://devfeed.tech/sources/watchtowr-labs.md>)

Topics: [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>)

Tags: [active-exploitation](<https://devfeed.tech/tags/active-exploitation.md>), [actively-exploited](<https://devfeed.tech/tags/actively-exploited.md>), [citrix](<https://devfeed.tech/tags/citrix.md>), [netscaler](<https://devfeed.tech/tags/netscaler.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

The article discusses active exploitation of Citrix NetScaler vulnerabilities, including remote code execution in a default configuration. It criticizes Citrix for not communicating the issue directly and says affected appliances should be taken offline. It also describes watchTowr's client exposure mitigation capabilities.

### Source excerpt

God damn it, we're back in the room again. Yes, that sound in your ears is screaming. The footgun has gone off again, shockingly, and we are yet again dealing with a situation where the entire world apparently knew about Citrix NetScaler CVEs before Citrix had woken up

## What the bliss taught us

DevFeed: [What the bliss taught us](<https://devfeed.tech/articles/what-the-bliss-taught-us-18901.md>)

Original publisher: [Read original article](<https://daniel.haxx.se/blog/2026/08/03/what-the-bliss-taught-us/>)

Author: Daniel Stenberg

Published: 2026-08-03T06:42:19Z

Content type: article

Language: en

Sources: [Daniel Stenberg](<https://devfeed.tech/sources/daniel-stenberg.md>)

Topics: [cURL](<https://devfeed.tech/topics/curl.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [bliss](<https://devfeed.tech/tags/bliss.md>), [cna](<https://devfeed.tech/tags/cna.md>), [curl](<https://devfeed.tech/tags/curl.md>), [curl-and-libcurl](<https://devfeed.tech/tags/curl-and-libcurl.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>), [security](<https://devfeed.tech/tags/security.md>), [vulnerability-reporting](<https://devfeed.tech/tags/vulnerability-reporting.md>)

### AI overview

curl's maintainers say pausing vulnerability reporting for July 2026 worked as intended: they received no reports through the expected channels, aside from one email sent privately that was ignored, and no emergency CVE assignments were needed. The break brought immediate relief and time for queued feature pull requests, neglected code, website and documentation work, and time away from keyboards. CNA rules were raised as a constraint because some critical vulnerabilities require a response within 72 hours; the maintainers believed emergency assignments by a "root" could cover the worst case, but that contingency was not needed. Existing support customers were told the pause would not affect them, and the excerpt says it did not. The supplied text ends mid-sentence, so it does not establish what happened with new customers or cover the full post.

### Source excerpt

At this exact moment curl's summer of bliss 2026 ends. We (the maintainers of curl) took the entire month of July off from vulnerability reporting and in this post I will try to explain how this went. (If you feel like skipping the wordy blab below, the single word answer is: fine) This was possibly ... Continue reading What the bliss taught us ->

## Observations on Anthropic's Vulnerability Disclosure Ledger

DevFeed: [Observations on Anthropic's Vulnerability Disclosure Ledger](<https://devfeed.tech/articles/observations-on-anthropic-s-vulnerability-disclosure-ledger-91449.md>)

Original publisher: [Read original article](<https://www.vulncheck.com/blog/anthropic-ledger>)

Author: Patrick Garrity

Published: 2026-06-09T00:00:00Z

Content type: opinion

Language: en

Sources: [VulnCheck](<https://devfeed.tech/sources/vulncheck.md>)

Topics: [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [open source maintenance](<https://devfeed.tech/topics/open-source-maintenance.md>), [CVSS v4.0](<https://devfeed.tech/topics/cvss-v4-0.md>), [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Exploit](<https://devfeed.tech/topics/exploit.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-discovered-vulnerabilities](<https://devfeed.tech/tags/ai-discovered-vulnerabilities.md>), [announcement](<https://devfeed.tech/tags/announcement.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [backlog](<https://devfeed.tech/tags/backlog.md>), [claude](<https://devfeed.tech/tags/claude.md>), [coordinated-vulnerability-disclosure](<https://devfeed.tech/tags/coordinated-vulnerability-disclosure.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [disclosure](<https://devfeed.tech/tags/disclosure.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [executive-order](<https://devfeed.tech/tags/executive-order.md>), [ledger](<https://devfeed.tech/tags/ledger.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [vulnerability-disclosure](<https://devfeed.tech/tags/vulnerability-disclosure.md>), [vulnerability-discovery](<https://devfeed.tech/tags/vulnerability-discovery.md>)

### AI overview

The excerpt finds that Anthropic's disclosure ledger had 27 fixed findings and no updates nearly three weeks after launch, despite an announcement citing 88 published advisories; it also omits CVE-2026-4747. Ten findings had passed the stated 90-day disclosure window, with 168 more approaching it. The policy's 90-day target, 45-day post-patch wait, possible 14-day extension, and broader exceptions leave the practical disclosure timeline unclear. The ledger omits CVE/GHSA mappings and the metrics behind severity ratings, including whether CVSS was used. Of 23,019 candidates, 1,596 had been sent to maintainers--467 validated and 1,129 reported without validation at maintainers' request--highlighting the human work required to triage, coordinate disclosure, and remediate findings at scale. The author presents the ledger as an early public example of a challenge facing maintainers and security response teams, and says its follow-through in the coming weeks will matter.

### Source excerpt

Public CVE disclosure volumes are surging across major software suppliers and open source projects, and the evidence increasingly points to AI-assisted vulnerability discovery as the driving force.

## VulnCheck Insights: CVE Context at the Hover of Your Cursor

DevFeed: [VulnCheck Insights: CVE Context at the Hover of Your Cursor](<https://devfeed.tech/articles/vulncheck-insights-cve-context-at-the-hover-of-your-cursor-91610.md>)

Original publisher: [Read original article](<https://www.vulncheck.com/blog/vulncheck-insights-chrome-extension>)

Author: Kimber Duke

Published: 2025-09-08T00:00:00Z

Content type: release

Language: en

Sources: [VulnCheck](<https://devfeed.tech/sources/vulncheck.md>)

Topics: [Business, Industry, Usability, User Experience, User Research, Web Strategy](<https://devfeed.tech/topics/business-industry-usability-user-experience-user-research-web-strategy.md>), [Usability](<https://devfeed.tech/topics/usability.md>), [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>)

Tags: [botnet](<https://devfeed.tech/tags/botnet.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [chatgpt](<https://devfeed.tech/tags/chatgpt.md>), [cursor](<https://devfeed.tech/tags/cursor.md>), [cve](<https://devfeed.tech/tags/cve.md>), [insights](<https://devfeed.tech/tags/insights.md>), [instant](<https://devfeed.tech/tags/instant.md>), [vulncheck](<https://devfeed.tech/tags/vulncheck.md>)

### AI overview

VulnCheck Insights is a Chrome extension that surfaces VulnCheck exploitation intelligence while users browse, so they can check a CVE's exploitation status without leaving the page. After installing it from the Chrome Web Store and adding a VulnCheck token in settings, users can hover over or click highlighted CVEs for exploitation context; highlighted CPEs and PURLs show associated CVE counts. The article says VulnCheck data may surface exploitation intelligence weeks before NVD or CISA's KEV list, but provides no comparative measurements. Support for other browsers is only being considered based on feedback.

### Source excerpt

Instead of bouncing between tabs, you now get instant, current context the moment a CVE appears on your screen.

## Cutting through the noise: How to prioritize Dependabot alerts

DevFeed: [Cutting through the noise: How to prioritize Dependabot alerts](<https://devfeed.tech/articles/cutting-through-the-noise-how-to-prioritize-dependabot-alerts-67552.md>)

Original publisher: [Read original article](<https://github.blog/security/application-security/cutting-through-the-noise-how-to-prioritize-dependabot-alerts/>)

Author: Andrea Griffiths

Published: 2025-04-29T16:00:39Z

Content type: tutorial

Language: en

Sources: [GitHub Blog](<https://devfeed.tech/sources/github-engineering.md>)

Topics: [Dependabot](<https://devfeed.tech/topics/dependabot.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [CVSS v4.0](<https://devfeed.tech/topics/cvss-v4-0.md>), [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>), [Prometheus alert rules](<https://devfeed.tech/topics/prometheus-alert-rules.md>)

Tags: [advanced-security](<https://devfeed.tech/tags/advanced-security.md>), [alert](<https://devfeed.tech/tags/alert.md>), [alert-fatigue](<https://devfeed.tech/tags/alert-fatigue.md>), [application-security](<https://devfeed.tech/tags/application-security.md>), [code-security](<https://devfeed.tech/tags/code-security.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [dependabot](<https://devfeed.tech/tags/dependabot.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [epss](<https://devfeed.tech/tags/epss.md>), [properties](<https://devfeed.tech/tags/properties.md>), [security](<https://devfeed.tech/tags/security.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [supply-chain-security](<https://devfeed.tech/tags/supply-chain-security.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability-research](<https://devfeed.tech/tags/vulnerability-research.md>), [web-application-security](<https://devfeed.tech/tags/web-application-security.md>)

### AI overview

The article explains how software teams can prioritize Dependabot vulnerability alerts by combining CVSS severity, EPSS exploitation likelihood, and repository context. It also describes using auto-triage rules to manage alerts consistently and reduce alert fatigue.

### Source excerpt

Learn how to effectively prioritize alerts using severity (CVSS), exploitation likelihood (EPSS), and repository properties, so you can focus on the most critical vulnerabilities first.

## Custom auto-triage rules for Dependabot alerts (public beta)

DevFeed: [Custom auto-triage rules for Dependabot alerts (public beta)](<https://devfeed.tech/articles/custom-auto-triage-rules-for-dependabot-alerts-public-beta-73367.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2023-09-14-custom-auto-triage-rules-for-dependabot-alerts-public-beta>)

Author: Kevin Duck

Published: 2023-09-14T17:34:02Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [Dependabot](<https://devfeed.tech/topics/dependabot.md>), [rule-engine](<https://devfeed.tech/topics/rule-engine.md>), [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>)

Tags: [advanced-security](<https://devfeed.tech/tags/advanced-security.md>), [alert-fatigue](<https://devfeed.tech/tags/alert-fatigue.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [api](<https://devfeed.tech/tags/api.md>), [beta](<https://devfeed.tech/tags/beta.md>), [create](<https://devfeed.tech/tags/create.md>), [custom](<https://devfeed.tech/tags/custom.md>), [dependabot](<https://devfeed.tech/tags/dependabot.md>), [false-positives](<https://devfeed.tech/tags/false-positives.md>), [public](<https://devfeed.tech/tags/public.md>), [public-beta](<https://devfeed.tech/tags/public-beta.md>), [rules](<https://devfeed.tech/tags/rules.md>), [triage](<https://devfeed.tech/tags/triage.md>)

### AI overview

Custom Dependabot auto-triage rules can dismiss matching current and future alerts indefinitely or snooze them until a patch is released, helping filter false positives and manage alerts in bulk. Auto-dismissed alerts remain reviewable with the `resolution:auto-dismissed` filter, and dismissal activity appears in webhooks, REST, GraphQL, and the audit log. These alerts close without a notification or new pull request; if alert metadata changes so the rule no longer applies, Dependabot reopens the alert. Users can also reopen alerts manually, after which that alert will not be auto-dismissed again by another auto-dismiss rule. Rules are free for open source repositories; GitHub Advanced Security customers can manage them across private repositories.

### Source excerpt

Auto-triage rules are a powerful tool to help you reduce false positives and alert fatigue substantially, while better managing your alerts at scale. Starting today, you can now create your...

## Dependabot alerts now automatically dismiss false positives for npm (public beta)

DevFeed: [Dependabot alerts now automatically dismiss false positives for npm (public beta)](<https://devfeed.tech/articles/dependabot-alerts-now-automatically-dismiss-false-positives-for-npm-public-beta-73538.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2023-05-02-dependabot-alerts-now-automatically-dismiss-false-positives-for-npm-public-beta>)

Author: Kevin Duck

Published: 2023-05-02T20:39:25Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [Dependabot](<https://devfeed.tech/topics/dependabot.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>), [npm](<https://devfeed.tech/topics/npm.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [account](<https://devfeed.tech/tags/account.md>), [actions](<https://devfeed.tech/tags/actions.md>), [addition](<https://devfeed.tech/tags/addition.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [beta](<https://devfeed.tech/tags/beta.md>), [dependabot](<https://devfeed.tech/tags/dependabot.md>), [false-positives](<https://devfeed.tech/tags/false-positives.md>), [impact](<https://devfeed.tech/tags/impact.md>), [long-running](<https://devfeed.tech/tags/long-running.md>), [npm](<https://devfeed.tech/tags/npm.md>), [public](<https://devfeed.tech/tags/public.md>), [public-beta](<https://devfeed.tech/tags/public-beta.md>), [running](<https://devfeed.tech/tags/running.md>), [tests](<https://devfeed.tech/tags/tests.md>), [this](<https://devfeed.tech/tags/this.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Dependabot now auto-dismisses some npm development dependency alerts that match GitHub-curated vulnerability patterns indicating limited impact or low likelihood of exploitation. The public beta is on by default for public repositories and opt-in for private repositories; repository admins can change the setting in Code Security. GitHub estimates that 15% of low-impact npm alerts will be dismissed. Dismissals generate no notification or pull request, but are recorded as timeline events and supported in webhooks, REST, GraphQL, and the audit log; the closed alert list can be filtered with `resolution:auto-dismissed`. Users can reopen an alert, and Dependabot will reopen it automatically if metadata changes invalidate the dismissal. Manually reopening prevents that alert from being auto-dismissed again. The feature is available for free repositories and GitHub Enterprise Cloud, and for GitHub Enterprise Server 3.10.

### Source excerpt

Starting today, Dependabot will be able to auto-dismiss npm alerts that have limited impact (e.g. long-running tests) or are unlikely to be exploitable. With this ship, Dependabot will cut false...

## Dependabot relieves alert fatigue from npm devDependencies

DevFeed: [Dependabot relieves alert fatigue from npm devDependencies](<https://devfeed.tech/articles/dependabot-relieves-alert-fatigue-from-npm-devdependencies-68017.md>)

Original publisher: [Read original article](<https://github.blog/security/supply-chain-security/dependabot-relieves-alert-fatigue-from-npm-devdependencies/>)

Author: Eric Tooley

Published: 2023-05-02T20:36:16Z

Content type: release

Language: en

Sources: [GitHub Blog](<https://devfeed.tech/sources/github-engineering.md>)

Topics: [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [Dependabot](<https://devfeed.tech/topics/dependabot.md>), [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>), [npm](<https://devfeed.tech/topics/npm.md>), [npm-workspaces](<https://devfeed.tech/topics/npm-workspaces.md>)

Tags: [alert-fatigue](<https://devfeed.tech/tags/alert-fatigue.md>), [dependabot](<https://devfeed.tech/tags/dependabot.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [false-positives](<https://devfeed.tech/tags/false-positives.md>), [npm](<https://devfeed.tech/tags/npm.md>), [security](<https://devfeed.tech/tags/security.md>), [supply-chain-security](<https://devfeed.tech/tags/supply-chain-security.md>)

### AI overview

GitHub has released a public beta feature that uses curated rules and contextual metadata to automatically dismiss likely false positive Dependabot alerts for npm devDependencies. GitHub says the feature is expected to reduce npm alerts by about 15%; it is enabled by default for public repositories and can be enabled by private repository administrators.

### Source excerpt

A new alert rules engine for Dependabot leverages alert metadata to identify and auto-dismiss up to 15% of alerts as false positives.

## The VulnCheck 2022 Exploited Vulnerability Report - A Year Long the CISA KEV Catalog - Blog - VulnCheck Review of the CISA KEV Catalog

DevFeed: [The VulnCheck 2022 Exploited Vulnerability Report - A Year Long the CISA KEV Catalog - Blog - VulnCheck Review of the CISA KEV Catalog](<https://devfeed.tech/articles/the-vulncheck-2022-exploited-vulnerability-report-a-year-long-the-cisa-kev-catalog-blog-vulncheck-review-of-the-cisa-kev-catalog-91436.md>)

Original publisher: [Read original article](<https://www.vulncheck.com/blog/2022-cisa-kev-review>)

Author: Jacob Baines

Published: 2023-03-02T00:00:00Z

Content type: article

Language: en

Sources: [VulnCheck](<https://devfeed.tech/sources/vulncheck.md>)

Topics: [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [cybersecurity and infrastructure security agency](<https://devfeed.tech/topics/cybersecurity-and-infrastructure-security-agency.md>), [Exploit](<https://devfeed.tech/topics/exploit.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [NVD](<https://devfeed.tech/topics/nvd.md>), [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>)

Tags: [2022](<https://devfeed.tech/tags/2022.md>), [22](<https://devfeed.tech/tags/22.md>), [added](<https://devfeed.tech/tags/added.md>), [backlog](<https://devfeed.tech/tags/backlog.md>), [blog](<https://devfeed.tech/tags/blog.md>), [botnets](<https://devfeed.tech/tags/botnets.md>), [browser](<https://devfeed.tech/tags/browser.md>), [buffer-overflow](<https://devfeed.tech/tags/buffer-overflow.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [cisa](<https://devfeed.tech/tags/cisa.md>), [cisa-kev](<https://devfeed.tech/tags/cisa-kev.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [it](<https://devfeed.tech/tags/it.md>), [kev](<https://devfeed.tech/tags/kev.md>), [kev-catalog](<https://devfeed.tech/tags/kev-catalog.md>), [report](<https://devfeed.tech/tags/report.md>), [review](<https://devfeed.tech/tags/review.md>), [vulncheck](<https://devfeed.tech/tags/vulncheck.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

CISA added 557 CVEs to its Known Exploited Vulnerability Catalog in 2022, growing it from 311 to 868 entries. Only 93 additions carried 2022 CVE identifiers, reflecting a substantial backlog of older exploited flaws; the catalog records vulnerabilities that have been exploited, not necessarily ones still under active exploitation. VulnCheck classifies 200 additions as initial-access vulnerabilities and links 122 to ransomware, while noting that threat-actor, botnet, and ransomware associations require intelligence beyond the catalog itself. For 2022-published CVEs with public exploit or exploitation information, 11% reached KEV on or before that information appeared, 41% within a week, and 48% later. The report cautions that this timing measure excludes cases without public evidence and can reflect delays in disclosure or vendor advisories, so KEV should not be treated as an early-warning system. It recommends prioritizing exploitable initial-access flaws and maintaining software inventory and patching, while emphasizing operating systems, desktop applications, browsers, IoT, and server software.

### Source excerpt

A review of the vulnerabilities added to the CISA KEV Catalog in 2022. VulnCheck examines which vulnerabilities were added in 2022, who exploited them, and how long it took to add them to the Catalog.

## Dependabot alerts are now ranked by most important priority

DevFeed: [Dependabot alerts are now ranked by most important priority](<https://devfeed.tech/articles/dependabot-alerts-are-now-ranked-by-most-important-priority-73965.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2022-07-15-dependabot-alerts-are-now-ranked-by-most-important-priority>)

Author: Kevin Duck

Published: 2022-07-15T20:24:20Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [Dependabot](<https://devfeed.tech/topics/dependabot.md>), [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>)

Tags: [alert](<https://devfeed.tech/tags/alert.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [cvss-score](<https://devfeed.tech/tags/cvss-score.md>), [dependabot](<https://devfeed.tech/tags/dependabot.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

GitHub has added a "Most Important" sort to the Dependabot alerts repository list, using CVSS score along with vulnerability impact, relevance, actionability, and factors such as vulnerable function usage and dependency scope. The sort does not affect Dependabot pull requests, organization-level alert lists, or the GraphQL API.

### Source excerpt

Dependabot alerts will now be easier to prioritize with a new "Most Important" sort. For the alerts repository list view, by default, alerts will be sorted in a way to...

## Dependabot alerts: persisted after fix, now one per advisory

DevFeed: [Dependabot alerts: persisted after fix, now one per advisory](<https://devfeed.tech/articles/dependabot-alerts-persisted-after-fix-now-one-per-advisory-74170.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2022-02-08-dependabot-alerts-persisted-after-fix-now-one-per-advisory>)

Author: Sidi Merzouk

Published: 2022-02-08T21:10:49Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [Dependabot](<https://devfeed.tech/topics/dependabot.md>), [CVE fatigue](<https://devfeed.tech/topics/cve-fatigue.md>)

Tags: [dependabot](<https://devfeed.tech/tags/dependabot.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [security](<https://devfeed.tech/tags/security.md>), [security-advisories](<https://devfeed.tech/tags/security-advisories.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

Dependabot alerts now remain visible in the closed tab after fixes and receive unique numeric identifiers. Alerts are displayed individually for each advisory and manifest, with titles that give developers more useful advisory details. The changes do not affect alert email digests, notifications, Dependabot pull requests, or the GraphQL API.

### Source excerpt

Today, we're shipping improvements to Dependabot alerts that help you more easily understand and remediate vulnerabilities from dependencies in your codebase. Persisted Dependabot alerts Developers can now view alerts that...