BSI report 2026: eight days to the first known exploitation of a vulnerability

On 19 November 2026, the German Federal Office for Information Security (BSI) published its annual report on the state of IT security in Germany. The agency now rates the situation in cyberspace as tense to critical. It cites the geopolitical situation and the fast development of artificial intelligence (AI) as the reasons.
What has got worse, according to the BSI
For the first time, the BSI combines the risk factors in cyberspace into one figure: the BSI Cyber Index (BSI CX). It averaged 170 points over the reporting period, 50 percent more than in the previous reporting period.
Every day, 160 new vulnerabilities in IT systems became known, 35 percent more than in the previous year.
The third figure concerns the span between a vulnerability becoming known and its first known exploitation. The BSI calls it time-to-exploit. In the previous reporting period, this took 53 days on average. In the current one it was 25 days, and in the second quarter of 2026 only 8. The BSI expects advanced AI models to continue this trend.
Why eight days matter for your company
If you install security updates once a month, an available update can wait around 30 days in the worst case. By our calculation, that's almost four times the eight days the BSI reports for the second quarter of 2026. And the BSI's eight days already start when the vulnerability becomes known, not when the update arrives.
The BSI also writes that attackers today often know about vulnerabilities before they are disclosed or before a patch is available. A patch is the vendor's update that closes the gap.
We draw two conclusions from this. First, the patch process for systems reachable from the internet has to be measured in days. Second, for the period without a patch, what counts is how little is reachable from outside and how well every access point is secured.
Who the BSI sees at particular risk
"Those who are easy targets get attacked," the BSI writes. As in previous years, the agency names small and medium-sized enterprises (SMEs) and local authorities as particularly vulnerable targets. In addition, fewer than half of the users of digital applications used basic security measures.
What NIS-2 and DORA require of management
Germany implements NIS-2 through the BSI Act (BSIG). For companies that count as important or essential entities under it, handling vulnerabilities is a legal duty. Section 30 BSIG requires, among other things, vulnerability handling and disclosure, and multi-factor or continuous authentication (subsection 2, nos. 5 and 10). With multi-factor authentication, a password alone isn't enough to log in. You also need a second factor, such as a code on your phone.
Under section 38 BSIG, management must implement these measures and oversee their implementation. Its members must also attend training regularly. Once a company becomes aware of a serious security incident (erheblicher Sicherheitsvorfall), fixed reporting deadlines apply. It must send an early warning without undue delay, at the latest within 24 hours, and an incident notification without undue delay, at the latest within 72 hours. A final report follows no later than one month after that notification, or first a progress report if the incident is still ongoing (section 32 BSIG; the duty applies once the reporting channel is in place).
For financial entities within its scope, such as credit institutions, payment institutions, investment firms and insurers, the EU's Digital Operational Resilience Act (DORA) has applied since 17 January 2025. Under Article 5(2)(a), the management body bears the ultimate responsibility for managing the entity's ICT risk. ICT stands for information and communication technology. Members of the management body must actively keep their knowledge up to date, including through regular specific training (Article 5(4)).
Both frameworks place responsibility explicitly with management. The eight days from the report therefore belong on the management agenda.
What management should do now
In our view, these five steps belong in the coming weeks.
Ask for the patch time as a number. Over the last three months, how many days passed between the release of a security update and its installation on the systems reachable from the internet? If the figure is above eight days, you have a concrete starting point.
Keep a list of all systems reachable from outside. These include VPN gateways, firewalls, mail servers and remote maintenance access. Each system needs a responsible person and a route for emergency patches that doesn't wait for the next maintenance window.
Secure remote access and administrator accounts with multi-factor authentication. For entities under the BSI Act, section 30 names it explicitly.
Rehearse the reporting chain. Who decides whether an incident is serious enough to report, and who sends the report within 24 hours? A tabletop exercise with management, IT and communications shows where the chain breaks.
Agree on a regular report. Three figures per quarter are enough to start with. They are the patch time for reachable systems, the share of access points with multi-factor authentication and the number of open critical vulnerabilities. This turns the oversight required by section 38 BSIG and Article 5 DORA into a routine.
How we support you
As an external CISO (vCISO), Cybervize takes on the information security function for mid-sized companies and financial service providers. Our platform OdySecure makes measures, responsibilities and evidence manageable, so that management can document its oversight.
Sources: BSI press release of 19 November 2026 (German), annual report "Die Lage der IT-Sicherheit in Deutschland 2026", BSI Act, section 30, section 32 and section 38 (German), DORA regulation on EUR-Lex.
