Skip to content

Category: Vulnerabilities & Advisories

Only 8 Days Until the Attack

The 2026 report by Germany's Federal Office for Information Security (BSI) shows how much the window for defenders has shrunk: in the second quarter of 2026, an average of just 8 days passed between a vulnerability becoming known and its first exploitation, compared with 47 days a year earlier. This article puts the figure into context, shows recent examples, and explains how to adapt your patch management – from prioritization and emergency updates to NIS2 requirements.

Published Approx. 17 min read Author: Rootsektor Editorial Team

In short: According to the BSI's 2026 report, the 8 days until a newly disclosed vulnerability is first exploited are an average for the second quarter of 2026; across the full reporting period, the average was 25 days, down from 53 days in the previous reporting period. Some vulnerabilities are even exploited before a patch is released. Close critical vulnerabilities in internet-facing systems within hours rather than weeks, prioritize by actual exploitation rather than by CVSS score alone, and check systems that were patched late for signs of an attack. Information as of November 19, 2026 – we will update this article as the situation develops.

What the BSI's 2026 report shows

On November 19, 2026, the BSI published its annual report “The State of IT Security in Germany in 2026” (BSI press release). It covers the period from July 1, 2025, to June 30, 2026 (BSI report online) and rates the situation as “tense to critical.” That is a deterioration compared with the previous reporting period, which the BSI had rated as “tense” (BSI report (PDF)). The BSI cites the rapid development of artificial intelligence and the rise in attacks via vulnerabilities as the main reasons.

The most striking figure concerns the so-called time-to-exploit, the time between a vulnerability becoming known and its first exploitation. According to the BSI, it averaged 53 days in the previous reporting period, 25 days in the current reporting period, and only 8 days in the second quarter of 2026 (BSI report (PDF)).

The decline has recently accelerated. According to the chart in the report, the figure was still 61 days in the third quarter of 2024, 47 in the second quarter of 2025, 32 in the fourth quarter of 2025, 16 in the first quarter of 2026, and 8 days in the second quarter of 2026 (BSI report (PDF)). The BSI puts the drop from 53 to 8 days at 85 percent. However, this compares the average of the previous reporting period with a single quarter; between the two reporting periods, the figure fell from 53 to 25 days, a decrease of just over half.

Referring to high-performance AI, BSI President Claudia Plattner speaks of tools “that enable cyberattacks in unprecedented volumes and at unprecedented speeds.” According to the BSI, advanced AI models will shorten the time-to-exploit even further; attackers often know about vulnerabilities before they are published or a patch is available (BSI press release).

What the 8 days mean – and what they don't

The 8 days are an average for a single quarter: many vulnerabilities are exploited much faster, others later. As its source, the BSI cites its vulnerability statistics, which are based on the NVD, CVE, and EUVD databases, reflect the global situation, and explicitly exclude zero-day vulnerabilities. The report does not disclose how the BSI determines the date of first exploitation; according to its methodology section, the statistics themselves only cover newly disclosed vulnerabilities (BSI report (PDF)). The figures therefore mainly show a trend and are not a deadline you can rely on.

This means that the most dangerous cases are missing from the figure: vulnerabilities that are exploited before they are even published. According to the BSI, the exploitation of vulnerabilities was the most important entry point for attackers in the reporting period, and zero-day vulnerabilities played a prominent role. The BSI expects that most of the vulnerabilities exploited in the next reporting period will already be zero-days (BSI report (PDF)).

Other analyses paint a similar picture, although each measures something different. According to CERT-EU, an exploited vulnerability was the entry point in 7 of 9 significant security incidents at EU institutions in 2025; attacks on unpatched edge devices such as firewalls and VPN appliances had the greatest impact (CERT-EU (PDF)).

Mandiant estimates the mean time-to-exploit for 2025 at minus 7 days: on average, vulnerabilities were exploited before a patch was released (Mandiant). According to VulnCheck, around 23 percent of the vulnerabilities newly recorded as exploited in the first half of 2026 were attacked on or before the day their CVE was published, down from almost 29 percent in 2025 (VulnCheck (PDF)). Rapid7 puts the time until high-severity vulnerabilities were exploited in the third quarter of 2026 at 3 days on average (Rapid7).

Defenders, by contrast, are slower. According to Verizon's Data Breach Investigations Report, organizations fully remediated only 26 percent of the critical vulnerabilities in the Known Exploited Vulnerabilities (KEV) catalog of the US Cybersecurity and Infrastructure Security Agency (CISA) in 2025, taking a median of 43 days (Verizon DBIR 2026 (PDF)). Amazon recommends measuring deadlines for patches and mitigations for critical vulnerabilities in internet-facing systems in hours: deadlines of 7 or 30 days assume a time buffer that no longer exists (Amazon).

Five examples from recent months

Cases from the report and from our blog show how short this window has become:

  • React2Shell (December 2025): For the critical vulnerability CVE-2025-55182 in React Server Components, the BSI observed waves of attacks just a few hours after a proof of concept became known on December 4, 2025 (BSI report (PDF)). Almost 15,000 web applications in Germany were vulnerable; by mid-December, only about half had been patched (BSI, Dec 15, 2025 (PDF)).
  • Ivanti EPMM (January 2026): According to the report, attackers had already exploited two critical vulnerabilities in Ivanti Endpoint Manager Mobile before they were published on January 29, 2026, including in Germany. The BSI advised restoring compromised systems from a secure backup or reinstalling them, then installing the update and changing all associated credentials (BSI report (PDF)).
  • php2shell (October 2026): Amazon recorded an exploitation attempt on October 17, 2026, four days before the vulnerabilities were published (Amazon). Since October 26, 2026, the European Union Vulnerability Database (EUVD) has listed them as exploited (EUVD-2026-107260). For background, see our article on php2shell.
  • Broccoli2Shell (October 2026): Node.js disclosed the vulnerability in the Brotli decoder together with updates on October 21, 2026 (Node.js); since October 27, 2026, the EUVD has listed it as exploited (EUVD-2026-108169). Read more in our article on Broccoli2Shell.
  • Java4Shell (November 2026): On November 18, 2026, one day after the vulnerability was published, the BSI pointed to initial exploitation attempts observed by the security company GreyNoise. According to the BSI, no successful attacks are known so far, and because exploitation is complex, it does not expect widespread attacks (BSI, Nov 18, 2026 (PDF)). Details are in our article on Java4Shell.

The examples show a common pattern: often only hours to a few days pass between a vulnerability becoming known and the first attacks or attack attempts, and some vulnerabilities are exploited even earlier.

More figures from the report

The report contains further figures that matter for patch management (BSI report (PDF)):

  • More vulnerabilities: Worldwide, an average of 160 new vulnerabilities became known every day, 35 percent more than in the previous reporting period; over the entire reporting period, almost 6,000 new vulnerabilities had a critical severity rating.
  • Greatest damage: According to the BSI, attackers caused the greatest damage by exploiting vulnerabilities. At the BSI honeypot, a decoy system for attackers, exploitation attempts rose by 48 percent and scans for vulnerable systems by 57 percent.
  • Growing attack surface: The Attack Surface Score, which the BSI uses to measure the attack surface in Germany, rose by 117 percent.
  • Outdated servers: At the end of October 2025, 92 percent of the roughly 33,000 known on-premises Exchange servers in Germany with publicly accessible Outlook Web Access were still running outdated versions.
  • Small businesses: According to the BSI, vulnerable internet-facing systems in Germany mostly belong to small and medium-sized enterprises. In the BSI's Cyber Risk Check (CyberRisikoCheck), a security assessment carried out by BSI-trained IT service providers, participating small and micro businesses met, on average, just under 55 percent of the 27 minimum requirements assessed.
  • AI as an accelerator: According to the BSI, agentic AI finds vulnerabilities, develops exploits at the same time, and can chain vulnerabilities into new attack paths. As a result, seemingly less critical vulnerabilities are also becoming more important.

How to adapt your patch management

The BSI recommends installing patches for vulnerabilities with a critical or high CVSS rating without delay, especially on exposed systems, and keeping the attack surface small (BSI report (PDF)). An IT security information notice from June 2026 is more specific: patch management must be able to review and assess vulnerabilities and roll out the necessary patches within minutes to a few hours at most; a few days is no longer fast enough (BSI, Jun 22, 2026 (PDF)). This translates into six steps:

  1. Know your inventory: Maintain an inventory of all applications and systems, including whether they can be reached from the internet (BSI, Jun 22, 2026 (PDF)). Also record components in third-party software and at service providers: in the case of React2Shell, the BSI assumes that not all operators knew their web applications contained the vulnerable component (BSI, Dec 15, 2025 (PDF)). Keep a separate list of systems without vendor support, because they no longer receive security updates.
  2. Exposed systems first: Internet-facing systems, especially perimeter systems such as firewalls and VPN gateways, take priority (BSI, Jun 22, 2026 (PDF)). CERT-EU recommends remediating critical vulnerabilities in exposed systems within days, not weeks (CERT-EU).
  3. Prioritize by exploitation: According to the BSI, focusing on the CVSS base score alone is not enough (BSI, Jun 22, 2026 (PDF)). Address vulnerabilities that are demonstrably being exploited first: ENISA's EUVD maintains a continuously updated list of exploited vulnerabilities (ENISA (PDF)). In addition, the Exploit Prediction Scoring System (EPSS) estimates the probability that a vulnerability will be exploited in the next 30 days; if exploitation is already known, that information takes precedence, according to FIRST, which publishes EPSS (FIRST).
  4. Automate, but with a fallback: The BSI names the automated installation of security patches as an effective measure, especially for smaller companies (BSI report (PDF)). Check in advance where full automation is possible, and keep backups and a fallback ready, because patches rolled out without testing can disrupt business-critical processes (BSI, Jun 22, 2026 (PDF)).
  5. Define an emergency process: Decide in advance who approves an emergency patch and how it is tested and rolled out on an accelerated basis. If no patch is available yet, compensating controls such as access restrictions, network segmentation, or a web application firewall can help (CERT-EU). For critical or already exploited vulnerabilities, the BSI says you should consider disconnecting selected exposed systems from the internet until the patch has been installed (BSI, Jun 22, 2026 (PDF)).
  6. Check for compromise after late patching: According to the BSI, patching alone is not enough after zero-days or patches installed late; the systems may already be compromised and must be actively examined (BSI report (PDF)). Amazon advises searching for traces back to the earliest known exploitation, not just back to the disclosure date (Amazon). If you have a concrete suspicion, a compromise assessment clarifies whether attackers are or were active without being noticed; if an attack is already visible, report the emergency.

What NIS2, DORA, and the Cyber Resilience Act require

For companies covered by NIS2, vulnerability management is a legal obligation. The German implementing act was promulgated in the Federal Law Gazette on December 5, 2025 (BGBl. 2025 I No. 301). Under Section 30 of the German BSI Act (BSIG), essential and important entities (in German: besonders wichtige und wichtige Einrichtungen) must, among other things, take security measures in the acquisition, development, and maintenance of their IT, “including vulnerability handling and disclosure” (Section 30 BSIG). Management must implement and monitor these measures and is liable for culpable breaches of duty (Section 38 BSIG).

For vulnerability management, the BSI lists measures such as regularly installing updates on all relevant systems, prioritizing security-critical vulnerabilities, and closing known vulnerabilities before they can be exploited (BSI NIS2 information package). The BSI's IT-Grundschutz (IT baseline protection) also requires that patches be assessed and prioritized promptly after publication and that a decision be made on installing them; if a patch is not installed, the decision and the reasons must be documented (BSI OPS.1.1.3 (PDF)). The BSI is currently transitioning IT-Grundschutz step by step to “Grundschutz++”; the existing IT-Grundschutz remains usable during a transition period of several years (BSI, Grundschutz++).

For most financial entities, the regulatory technical standards under DORA, the EU's Digital Operational Resilience Act, specify the requirements. They call for patch management procedures that identify available patches using automated tools where possible, provide emergency procedures for patching, and set deadlines for installation as well as escalation procedures if those deadlines are missed (Commission Delegated Regulation (EU) 2024/1774). For financial entities with a simplified ICT risk management framework under Article 16 of DORA, leaner requirements without these deadline and escalation rules apply (Commission Delegated Regulation (EU) 2024/1774).

Since September 11, 2026, manufacturers of products with digital elements have been subject to reporting obligations under the Cyber Resilience Act. For actively exploited vulnerabilities in their products, they must submit an early warning within 24 hours and a vulnerability notification within 72 hours; the final report follows no later than 14 days after a corrective or mitigating measure becomes available (Regulation (EU) 2024/2847). In Germany, the role of the coordinating computer security incident response team (CSIRT) is taken by CERT-Bund, the BSI's computer emergency response team (BSI report (PDF)).

Neither the BSIG nor the DORA standards prescribe fixed patch deadlines in days; companies must set and justify appropriate deadlines themselves (own research, as of November 19, 2026). Clarify how the requirements apply in your specific case, coordinated with your data protection and legal advisors.

Do you know which of your systems can be attacked from the internet? A vulnerability assessment examines your systems from the outside and, with authenticated scans, from the inside. It finds missing updates and outdated software and prioritizes the findings. A network penetration test shows how far an attacker could actually get via unpatched systems.

Checklist: patch management in 2026

  • Every system is inventoried, including whether it can be reached from the internet and the components in third-party software
  • Critical vulnerabilities in exposed systems have a deadline measured in hours, not weeks
  • Prioritization is based on actual exploitation (for example, according to the EUVD) and exposure, not only on the CVSS score
  • Security updates are installed automatically where possible, with backups and a fallback
  • An emergency process for critical patches is defined, with clear responsibilities and accelerated approval
  • Countermeasures are prepared for vulnerabilities without a patch, such as access restrictions or temporarily disconnecting systems from the internet
  • Systems patched late are checked for signs of an attack
  • Systems without vendor support have been replaced or isolated
  • BSI warnings are evaluated on an ongoing basis

Conclusion: patching at the attackers' pace

The 8 days in the BSI report are an average: many vulnerabilities are exploited faster, some even before a patch exists. A monthly patch cycle is therefore no longer sufficient for internet-facing systems. What matters is a complete inventory, prioritization based on actual exploitation, a well-practiced emergency process, and checking for possible compromise after late updates. This is how you shorten the time during which your systems are vulnerable.

Sources

All sources accessed on November 19, 2026.

Frequently asked questions

Do I have 8 days to patch after a new vulnerability is disclosed?

No. The 8 days are an average for the second quarter of 2026. Many vulnerabilities are exploited much faster, some even before they are published, and zero-days are not included in the figure at all. For critical vulnerabilities in internet-facing systems, the BSI recommends being able to install patches within a few hours, or better yet minutes (BSI, Jun 22, 2026 (PDF)).

Where does the figure of 8 days come from?

From the BSI's 2026 report. In it, the BSI reports the time-to-exploit for each quarter and names its own vulnerability statistics as the source, which are based on the NVD, CVE, and EUVD databases; the BSI does not disclose how it determines the date of first exploitation. Across the entire reporting period from July 1, 2025, to June 30, 2026, the average was 25 days, compared with 53 days in the previous reporting period (BSI report (PDF)).

Is it enough to install all updates automatically?

According to the BSI, automation is an effective measure, especially for smaller companies. However, it does not replace a complete inventory: without one, forgotten systems and bundled components remain unpatched. The BSI also recommends checking in advance where untested updates could jeopardize operations and keeping backups and a fallback ready (BSI, Jun 22, 2026 (PDF)).

Are there legal deadlines for patching?

Neither the German BSI Act nor the DORA standards prescribe fixed deadlines in days. However, entities covered by NIS2 must have vulnerability management in place under Section 30 BSIG, and most financial entities must set their own installation deadlines and emergency procedures under DORA. Since September 11, 2026, manufacturers have had to report actively exploited vulnerabilities in their products within 24 hours. Clarify how this applies in your specific case, coordinated with your data protection and legal advisors.

Share article

Contact

How quickly do you close critical vulnerabilities?

We find vulnerable and outdated systems in your environment, prioritize the findings, and check whether attackers have already exploited a vulnerability.

Get in touch+49 2932 465265-0

Author

Rootsektor Editorial Team

Team of Rootsektor IT-Security GmbH

Under this name, the team of Rootsektor IT-Security GmbH publishes articles on vulnerabilities, attack techniques, and defense. The company offers vendor-independent penetration testing, security services, and incident response and forensics, and is editorially responsible for the articles.

About Rootsektor

Transparency note: This article was created with the support of AI tools. Editorial responsibility for its content and statements lies with Rootsektor IT-Security GmbH.

Related services

Glossary terms

Blog

More articles

All articles
  • Vulnerabilities & Advisories

    Java4Shell: Critical Java Vulnerability and What to Do Now

    · Approx. 23 min read

    A critical flaw in the OpenJDK Base64 decoder can enable code execution on x86-64 processors with AVX-512 VBMI. Java 17, 21, 25, and 27 from the major vendors are affected.

  • Vulnerabilities & Advisories

    php2shell: Critical PHP Vulnerabilities and What to Do Now

    · Approx. 12 min read

    Two critical flaws in the PHP core let attackers run code on web servers without authentication. Which versions are affected, how the vulnerabilities work, and what you need to do now.