TL;DR: Older flaws are becoming active again when remediation lags and exposed instances stay reachable, Coalition reports. Exposure-led prioritisation now matters more than blanket patching because reachable services create the easiest attack path.
Editorial analysis by NHI Mgmt Group, based on content published by Coalition: “What’s Old Is New Again: Attackers Target Resurgent Vulnerabilities”.
By the numbers:
- Vulnerability exploitation was the leading initial access vector in 2025, accounting for 31% of all breaches.
Key questions
Q: Why does delayed patching continue to create risk even for older, well-publicized vulnerabilities?
A: Delayed patching keeps known attack paths open long after a flaw becomes public.
Q: What are the signs that a vulnerability prioritization model is failing?
A: The clearest signs are long delays on known exploited vulnerabilities, tickets that lack ownership, duplicate findings across tools, and high-severity work that never maps to real attack paths.
Q: What should teams do first when an older vulnerability becomes active again?
A: Start with exposure validation, not patch theatre.
Practitioner guidance
- Prioritise exposed vulnerabilities over inventory age Use external exposure, exploit evidence and asset criticality to rank remediation instead of treating all backlog items equally.
- Review third-party access paths and OAuth grants Identify connected applications, delegated tokens and broad permissions that could be abused without a software exploit.
- Separate hosted and self-managed remediation ownership Document who patches, who verifies and who escalates when a vulnerability sits inside a provider-managed platform.
Bottom line: Older vulnerabilities can become active threats again when remediation lags and exposed instances remain reachable.
Glossary terms: Resurgent Vulnerability, Exposure Window, Platform-Level Aggregation, Delegated trust
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Exposure windows, not disclosure dates, now define vulnerability risk. Older flaws remain dangerous when remediation lags and exposed instances stay reachable. That makes backlog age a poor proxy for actual safety, especially where management interfaces or hosted control planes are concerned. Practitioners need to treat live exposure as the governing variable, not publication history.
A few things that frame the scale:
- The median time to fully patch a vulnerability in CISA's Known Exploited Vulnerabilities catalog rose to 43 days, according to Verizon's 2026 Data Breach Investigations Report.
A question worth separating out:
Q: How should security teams handle shared responsibility for hosted software?
A: Teams should define who patches, who confirms success and who communicates residual risk before the issue is found. If a provider manages the platform, internal teams still need verification, escalation paths and a clear view of which assets remain exposed. Shared responsibility without explicit ownership is just delayed accountability.
👉 Read our full editorial: Resurgent vulnerabilities outpace patching and widen exposure windows