CLOUDEK · Vulnerability tracking

Urgent vulnerabilities feed

A build-time snapshot of vulnerabilities listed in CISA’s Known Exploited Vulnerabilities catalog during the last 30 UTC dates. This page is refreshed by hand, not live. Burning rows are CISA KEV entries added within 30 UTC days with ransomware campaign use listed as Known or an EPSS score of at least 0.5. Older entries with a Cloudek guide are retained but do not become burning solely because of that guide. This is not a scan of your systems.

The checked-in snapshot has not been refreshed. Empty counts are not a finding of zero vulnerabilities.

Actively exploited vulnerabilities this month — CISA KEV snapshot9 rows meet the stated burning rule; 3 rows have Cloudek guides. A dated CISA KEV and FIRST EPSS snapshot, not a scan of your systems.cloudek.Data generated 2026-11-13 · manually refreshed9BURNING ELIGIBLE30OTHER ELIGIBLE3GUIDE LINKEDCAPPED SNAPSHOT ROW COUNTS; NO ENVIRONMENT ASSESSMENT9 rows meet the published 30-day rule · not a system scan.CVE-2026-109618 · PHP Memory Corruption VulnerabilityPHP Group · PHPGuide linkedCVE-2026-109619 · PHP Stale Internal Request-State VulnerabilityPHP Group · PHPGuide linkedCVE-2026-21589 · Atlassian Multiple Products Files or DirectoriesAtlassian · Multiple ProductsEPSS ≥ 0.5Sources: CISA KEV and FIRST EPSS · generated 2026-11-13Not a scan of your systems · cloudekhosting.com

This page uses one same-origin request for a capped, dated build-time data file. It does not fetch CISA or FIRST in your browser, and it does not assess your environment. Check the linked source information before acting.

Source catalogs: CISA Known Exploited Vulnerabilities catalog · FIRST EPSS information

Loading snapshot…

Show the details

Burning now

Loading…

These rows were added to CISA KEV within 30 UTC days and have ransomware campaign use listed as Known or an EPSS score of at least 0.5. Guide-linked rows are retained in the feed but do not become burning solely because a guide exists.

Check whether you run it. If you do, follow the vendor’s fix and CISA’s required action.

Loading…

Other KEV entries

Loading…

This table includes other KEV entries added within 30 UTC days and older entries retained because a Cloudek guide exists. Guide-linked rows are prioritized. The generated data contains at most 25 entries total across both sections.

Check whether you run it. If you do, follow the vendor’s fix and CISA’s required action.

CVEVendor and productNameCISA addedEntry windowRansomware useEPSS raw scoreCISA deadline for US federal agenciesCISA required action
Loading…

How it works

A build script reads CISA’s public KEV catalog, keeps entries added no more than 30 UTC days ago, and asks FIRST’s EPSS API for scores in batches of up to 100 CVE IDs. Older catalog entries are retained only when a maintained Cloudek guide maps to the CVE. Burning means a row in the 30-day age window with CISA ransomware use listed as Known or an EPSS score at or above 0.5. The final data file contains no more than 25 rows across both sections. Within each section, guide-linked entries come first, followed by known ransomware use, higher EPSS score and newer CISA date.

CISA’s due date is labelled as a deadline for US federal agencies. It is not presented as a deadline for every organization. EPSS is shown as a raw score because this page does not convert it to a probability.

Frequently asked questions

Is this live threat monitoring? No. The file is generated manually and can be out of date. Check CISA and the affected vendor directly.

Does “Burning now” mean a product is affected in my environment? No. It applies the visible date, ransomware and EPSS rules to catalog rows. You need to confirm products and versions you run.

What does a missing EPSS score mean? It means a score was not available to the build. It is not a zero score or a pass.

What is in a CISA action? The required-action field is displayed as quoted text from the CISA KEV data row.

Was this helpful?