Live tracker of exploited and high-impact vulnerabilities
New vulnerabilities from CERTs, vendors, researchers and newsrooms in 180+ countries, checked automatically, with how widely each one is being exploited, warned about and covered.
Panic meter
Connecting- Researchers talking
- –
- News outlets covering
- –
- CERTs and agencies warning
- –
Distinct people and organisations discussing new vulnerabilities in the past 24 hours.
Trending now
Outbreak map
- Countries in the news
- –
- Agencies warning
- –
- Countries warned
- –
- Patient zero
- –
Daily panic
Vulnerabilities
GitLab vulnerabilities
Every GitLab vulnerability Vulnocalypse is tracking, newest first: whether it’s being exploited, which CERTs have warned about it and how widely it’s covered. Subscribe with the RSS feed for GitLab alerts.
- 70impact
Integer Overflow or Wraparound in GitLab
Public exploit code0 news outlets3 CERTs5 researchersCVSS 10.0 - 87impact
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab
Known exploited (KEV) (CISA)1 news outlets2 CERTs0 researchersCVSS 10.0 - 70impact
2026-019: Critical Vulnerability in GitLab Community and Enterprise Editions
Public exploit code3 news outlets12 CERTs0 researchersCVSS 10.0 - 46impact
Deserialization of Untrusted Data in GitLab
0 news outlets1 CERTs0 researchersCVSS 9.9 - 22impact
Acceptance of Extraneous Untrusted Data With Trusted Data in GitLab
0 news outlets0 CERTs0 researchersCVSS 4.6 - 21impact
Incorrect Authorization in GitLab
0 news outlets0 CERTs0 researchersCVSS 4.2 - 33impact
Incorrect Authorization in GitLab
0 news outlets0 CERTs0 researchersCVSS 7.7 - 35impact
Incorrect Authorization in GitLab
0 news outlets0 CERTs0 researchersCVSS 8.5 - 36impact
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in GitLab
0 news outlets0 CERTs0 researchersCVSS 8.7 - 18impact
Incorrect Authorization in GitLab
0 news outlets0 CERTs0 researchersCVSS 3.1 - 30impact
Incorrect Authorization in GitLab
0 news outlets0 CERTs0 researchersCVSS 5.3 - 31impact
Incorrect Authorization in GitLab
0 news outlets0 CERTs0 researchersCVSS 5.3 - 17impact
Incorrect Authorization in GitLab
0 news outlets0 CERTs0 researchersCVSS 2.7 - 27impact
Insertion of Sensitive Information into Log File in GitLab
0 news outlets0 CERTs0 researchersCVSS 6.2 - 19impact
Server-Side Request Forgery (SSRF) in GitLab
0 news outlets0 CERTs0 researchersCVSS 3.5 - 28impact
URL Redirection to Untrusted Site ('Open Redirect') in GitLab
0 news outlets0 CERTs0 researchersCVSS 5.8 - 22impact
Incorrect Authorization in GitLab
0 news outlets0 CERTs0 researchersCVSS 4.3 - 17impact
Incorrect Authorization in GitLab
0 news outlets0 CERTs0 researchersCVSS 2.7 - 34impact
Permissive Regular Expression in GitLab
0 news outlets0 CERTs0 researchersCVSS 8.2 - 22impact
Incorrect Privilege Assignment in GitLab
0 news outlets0 CERTs0 researchersCVSS 4.3 - 21impact
Incorrect Authorization in GitLab
0 news outlets0 CERTs0 researchersCVSS 4.2 - 30impact
Incorrect Authorization in GitLab
0 news outlets0 CERTs0 researchersCVSS 5.3 - 22impact
Insufficient Granularity of Access Control in GitLab
0 news outlets0 CERTs0 researchersCVSS 4.3 - 34impact
Improper Neutralization of Input Used for LLM Prompting in GitLab
0 news outlets0 CERTs0 researchersCVSS 7.3 - 21impact
Incorrect Authorization in GitLab
0 news outlets0 CERTs0 researchersCVSS 4.2 - 22impact
Incorrect Authorization in GitLab
0 news outlets0 CERTs0 researchersCVSS 4.3 - 22impact
Reliance on Untrusted Inputs in a Security Decision in GitLab
0 news outlets0 CERTs0 researchersCVSS 4.3 - 46impact
Integer Overflow or Wraparound in GitLab
0 news outlets1 CERTs0 researchersCVSS 9.9 - 45impact
Double Free in GitLab
0 news outlets1 CERTs0 researchersCVSS 9.9 - 42impact
Bytebase 0.12.0 before 1.0.1 Authentication Bypass via GitLab Self-Hosted Login
0 news outlets0 CERTs0 researchersCVSS 9.8 - 25impact
Use of Less Trusted Source in GitLab
0 news outlets1 CERTs0 researchersCVSS 4.3 - 27impact
Incorrect Authorization in GitLab
0 news outlets0 CERTs0 researchersCVSS 5.9 - 40impact
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in GitLab
0 news outlets1 CERTs0 researchersCVSS 7.5 - 18impact
Improper Cleanup on Thrown Exception in GitLab
0 news outlets0 CERTs0 researchersCVSS 3.1 - 30impact
Incorrect Authorization in GitLab
0 news outlets0 CERTs0 researchersCVSS 6.8 - 19impact
Use of Incorrectly-Resolved Name or Reference in GitLab
0 news outlets0 CERTs0 researchersCVSS 3.1 - 27impact
Insertion of Sensitive Information Into Sent Data in GitLab
0 news outlets0 CERTs0 researchersCVSS 4.3 - 22impact
Authorization Bypass Through User-Controlled Key in GitLab
0 news outlets0 CERTs0 researchersCVSS 4.3 - 20impact
Use of Cache Containing Sensitive Information in GitLab
0 news outlets0 CERTs0 researchersCVSS 3.5 - 17impact
Incorrect Authorization in GitLab
0 news outlets0 CERTs0 researchersCVSS 2.7 - 39impact
Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection') in GitLab
0 news outlets1 CERTs0 researchersCVSS 8.2
Sources
CERTs and cyber security agencies, national news outlets in every country we could find, vendor advisories, research blogs and the security press. Every source is polled on its own schedule, by RSS where possible and by headless browser where not. Broken feeds are repaired automatically; anything still failing is listed here.
Sources admin
Enter the admin token from your server’s .env file (ADMIN_TOKEN). It’s sent once to start a session and isn’t stored in this browser.
Recent sign-in activity
Pipeline, last 24 hours
How many articles each type of source produced, how many were read in full, and how many were linked to a vulnerability. “Unmatched” are articles that look like vulnerability news but couldn’t be linked; the reasons and examples show what to improve.
Add a source
Coverage
All sources
How it works
Vulnocalypse reads vulnerability registries, government CERTs, vendor advisories, research blogs and newsrooms around the clock, links everything that refers to the same vulnerability, and only shows what passes automated validation.
What gets into the feed
A vulnerability is admitted when it is corroborated, either through a published CVE record or through at least two independent organisations, and its impact score reaches 60 out of 100. Anything listed in a known-exploited catalogue is admitted regardless of score. Once admitted, an entry stays, so the feed never flickers.
Impact score
Up to 30 points for severity (CVSS, or inferred from the description when no score exists), 25 for exploitation, 15 for blast radius by product category (edge devices and identity systems score highest), 15 for attention from news, CERTs and researchers, 10 for EPSS exploitation probability, and 5 for pre-authentication. Every entry shows its breakdown.
Exploitation status
We only mark something exploited when there is a citable source: a KEV listing (CISA, VulnCheck or ENISA), a statement from the vendor or a government agency, CISA’s SSVC assessment, or at least two independent organisations reporting attacks with no later denial from the vendor. Phrases like “no evidence of exploitation” are detected and count against a claim.
Validation, without humans
Identifiers are checked against the CVE List; rejected or non-existent CVEs are dropped. Titles, vendors, products and CVSS come from the official record rather than from headlines. Wire stories syndicated across outlets are counted once. Roundups that list dozens of CVEs only count the ones they actually discuss. Reports without an identifier wait for corroboration and are merged into the right CVE once one is assigned. Every decision is logged and shown on each vulnerability’s page.
The Panic meter
Three numbers over the past 24 hours, counting only vulnerabilities first seen in the last 14 days: distinct researchers posting about them, distinct news organisations covering them, and distinct CERTs and agencies warning about them. Each is ranked against its own 90-day history, weighted 35% CERTs, 35% news and 30% researchers, and stretched so the top levels stay rare. Each day’s score is split across the vulnerabilities that caused it.
The outbreak map
The map shows two things for every country: how many national news outlets are covering new vulnerabilities, and whether the national CERT or cyber security agency has issued a warning. National outlets are read directly, through local-language Google News editions, and through GDELT, which attributes coverage in over 100 languages to its source country. International security press is left off the map so it shows national attention, not trade coverage. Replay the spread to watch a vulnerability travel from patient zero across the world.
Subscribe
- Everything (RSS), also as Atom and JSON Feed
- Exploited only and KEV-listed only
- Updates: new KEV listings, exploitation changes and public exploits for tracked vulnerabilities
- Per vendor:
/feed.xml?vendor=Fortinet, or by score:/feed.xml?min_score=80
Use it from an AI agent
Vulnocalypse runs a read-only MCP server. Add it to any MCP client as a remote server:
https://vulnocalypse.com/mcpTools: get_feed, search_vulnerabilities, get_vulnerability, check_exposure (send the products you run and get back anything that affects them), get_panic and explain_panic_day. The JSON API is documented at /api/docs.