Security flaw tracker: new CVEs today

From NVD and CISA, updated hourly · 09:34 UTC

Yesterday

112

11 critical · 26 today

Last 7 days

3,461

▼23% vs 7 before

Last 30 days

16,669

▲12% vs 30 before

Exploited, 30 days

35

CISA list: 1,766

Nov 1, 2026 (so far) · 26 new5 critical1 high12 medium2 low6 unscored· 7-day avg 555

240012000
Aug 4, 2026today

CriticalHighMediumLowNot scored yet7-day average

What they hit · 30d

  • Operating systems17%
  • Dev tools & libraries13%
  • WordPress & CMS10%
  • Business software7%
  • Browsers6%
  • Web apps5%
  • Other44%

Kind of flaw · 30d

  • Auth bypass & access23%
  • Memory corruption18%
  • Cross-site scripting8%
  • Remote code execution6%
  • Denial of service5%
  • Path traversal & file upload4%
  • Other37%

Vendors · 30d

  • Microsoft9%
  • Oracle Corporation6%
  • Linux6%
  • Google5%
  • Apple2%
  • Apache Software Foundation2%
  • Other70%

exploited in the wild: patch firstCISA KEV · 45 days

latest criticalCVSS 9+ · 48 hours

FAQ

Where do these numbers come from?+

From the U.S. National Vulnerability Database (NVD), which publishes every new CVE, and from CISA’s Known Exploited Vulnerabilities catalog, the official list of flaws attackers are using in the wild. DevHunt reads both every hour and only counts and sorts what they publish.

What is a CVE?+

A CVE (Common Vulnerabilities and Exposures) is a public ID for one security flaw in one product, like CVE-2026-12345. Each gets a description and usually a CVSS severity score from 0 to 10: critical is 9 and up, high 7 to 8.9, medium 4 to 6.9, low below 4.

Which day does a CVE count on?+

The UTC day NVD published it. Today’s bar fills up during the day, so it is lighter in the chart until the day is over. Rejected CVEs are not counted.

Why are some CVEs not scored yet?+

A CVE is published as soon as it is reserved and described; the CVSS score comes from the reporting organization or from NVD’s own analysis, which can take days or weeks. Those CVEs show as “not scored yet”.

How is a flaw sorted into a kind and an area?+

The kind comes from its CWE (the weakness type the CVE lists, e.g. CWE-79 is cross-site scripting). The area comes from keywords in the vendor, product and description: cars and vehicles, medical devices, industrial and energy, AI tools, WordPress, phones, browsers, routers and IoT, and so on. It is a plain rule, the same for every CVE, so it is good for trends but can misfile a single flaw.

Which flaws should I patch first?+

The ones in the “exploited in the wild” list that you run: attackers are already using them. After that, critical flaws in internet-facing software. Most CVEs are never exploited, so the daily total says more about how much is being found than about how much danger you are in.

Why are there so many more CVEs than a few years ago?+

More organizations can now hand out CVE IDs, open-source and WordPress plugin flaws are reported in bulk, and AI tools find bugs faster. The yearly count has risen every year: about 29,000 in 2023, 40,000 in 2024 and far more since.