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
PostgreSQL vulnerabilities
Every PostgreSQL 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 PostgreSQL alerts.
- 39impact
Silent channel-binding authentication downgrade via unsupported certificate algorithms
0 news outlets0 CERTs0 researchersCVSS 8.2 - 37impact
PostgreSQL pg_basebackup and pg_rewind can overwrite unrelated files of origin superuser choice
0 news outlets0 CERTs0 researchersCVSS 8.8 - 37impact
PostgreSQL refint allows stack buffer overflow and SQL injection
0 news outlets0 CERTs0 researchersCVSS 8.8 - 20impact
PostgreSQL REFRESH PUBLICATION allows SQL injection via table name
0 news outlets0 CERTs0 researchersCVSS 3.7 - 40impact
PostgreSQL SSL/GSS init causes denial of service, via uncontrolled recursion
0 news outlets0 CERTs0 researchersCVSS 7.5 - 25impact
PostgreSQL CREATE TYPE does not check multirange schema CREATE privilege
0 news outlets0 CERTs0 researchersCVSS 5.4 - 32impact
PostgreSQL pg_createsubscriber allows SQL injection via subscription name
0 news outlets0 CERTs0 researchersCVSS 7.2 - 37impact
PostgreSQL discloses MD5-hashed passwords via covert timing channel
0 news outlets0 CERTs0 researchersCVSS 6.5 - 22impact
PostgreSQL timeofday() can disclose portions of server memory
0 news outlets0 CERTs0 researchersCVSS 4.3 - 38impact
PostgreSQL libpq lo_* functions let server superuser overwrite client stack memory
0 news outlets0 CERTs0 researchersCVSS 8.8 - 22impact
PostgreSQL pg_restore_attribute_stats accepts values that cause query planning to read past end of stats array
0 news outlets0 CERTs0 researchersCVSS 4.3 - 36impact
Use of Hard-coded Cryptographic Key in the PostgreSQL Sidecar Service in Splunk Enterprise
0 news outlets0 CERTs0 researchersCVSS 8.8 - 41impact
PostgreSQL server undersizes allocations, via integer wraparound
0 news outlets0 CERTs0 researchersCVSS 8.8 - 20impact
PostgreSQL amcheck does not clear untrusted search path
0 news outlets0 CERTs0 researchersCVSS 3.8 - 40impact
PostgreSQL to_char heap buffer overflow executes arbitrary code
0 news outlets0 CERTs0 researchersCVSS 8.8 - 38impact
PostgreSQL refint plan cache type confusion executes arbitrary code
0 news outlets0 CERTs0 researchersCVSS 8.8 - 38impact
PostgreSQL tsvector and tsquery undersize allocations, via integer wraparound
0 news outlets0 CERTs0 researchersCVSS 8.8 - 40impact
PostgreSQL logical decoding can dlopen arbitrary file
0 news outlets2 CERTs0 researchersCVSS 7.2 - 38impact
PostgreSQL expression deparse allows SQL injection via EXTRACT argument
0 news outlets0 CERTs0 researchersCVSS 8.8 - 35impact
PostgreSQL ctid type confusion in selectivity estimator discloses derivative of arbitrary read
0 news outlets0 CERTs0 researchersCVSS 8.1 - 22impact
PostgreSQL ALTER TABLE ALTER TYPE resets extended statistics ownership
0 news outlets0 CERTs0 researchersCVSS 3.8 - 38impact
PostgreSQL 32-bit pltcl and plperl undersize allocations, via integer wraparound
0 news outlets0 CERTs0 researchersCVSS 8.8 - 30impact
PostgreSQL observable response discrepancy with non-default scram_iterations provides user existence oracle
0 news outlets0 CERTs0 researchersCVSS 5.3 - 37impact
PostgreSQL psql \unrestrict lets superuser of pg_dump origin server execute arbitrary code in psql client
0 news outlets0 CERTs0 researchersCVSS 8.8 - 21impact
PostgreSQL row security caching disregards role modifications
0 news outlets0 CERTs0 researchersCVSS 4.2 - 20impact
PostgreSQL ECPG integer underflow can crash the client
0 news outlets0 CERTs0 researchersCVSS 3.8 - 40impact
PostgreSQL pg_dump lets superuser of origin server execute arbitrary code in psql client
0 news outlets0 CERTs0 researchersCVSS 8.8 - 22impact
PostgreSQL ascii() function reads past end of buffer
0 news outlets0 CERTs0 researchersCVSS 4.3 - 40impact
PostgreSQL psql COPY FROM STDIN early failure processes data lines as psql commands
0 news outlets0 CERTs0 researchersCVSS 8.1 - 38impact
PostgreSQL type confusion via "internal" arguments
0 news outlets0 CERTs0 researchersCVSS 8.8 - 22impact
PostgreSQL pg_trgm picksplit reads past end of buffer
0 news outlets0 CERTs0 researchersCVSS 4.3 - 40impact
PostgreSQL type confusion in cursor CLOSE + DECLARE executes arbitrary code
0 news outlets0 CERTs0 researchersCVSS 8.8 - 23impact
PostgreSQL fails to check type USAGE privilege
0 news outlets0 CERTs0 researchersCVSS 4.3 - 40impact
PostgreSQL stack buffer overflow in argument match writes 0x0 and 0x1 to server memory
0 news outlets0 CERTs0 researchersCVSS 8.2 - 38impact
PostgreSQL regexp heap buffer overflow executes arbitrary code
0 news outlets0 CERTs0 researchersCVSS 8.8 - 33impact
PostgreSQL pgcrypto, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext
0 news outlets0 CERTs0 researchersCVSS 6.5 - 39impact
PostgreSQL fuzzystrmatch writes effectively-arbitrary addresses, via integer wraparound
0 news outlets0 CERTs0 researchersCVSS 8.8 - 38impact
PostgreSQL pg_dump heap buffer overflow executes arbitrary code
0 news outlets0 CERTs0 researchersCVSS 8.8 - 38impact
PostgreSQL plperl tied object heap buffer overflow executes arbitrary code
0 news outlets0 CERTs0 researchersCVSS 8.8 - 41impact
PostgreSQL missing validation of multibyte character length executes arbitrary code
0 news outlets0 CERTs0 researchersCVSS 8.8
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.