Vulnerabilities
Loading exploited flaws
Filters the list below. Nothing you type is sent anywhere.
How long do we have to patch?
Flaws CISA confirms attackers are using, measured from today. A bar to the right is time left before the US federal deadline; a bar to the left is how long ago it passed. Use the deadline as an upper limit for your own patching.
Source: CISA Known Exploited Vulnerabilities catalog. The deadline binds US federal agencies only.
No software list loaded, so this is the general ranking. Add yours under to see which versions you run are affected. It stays in this browser.
How the patch queue rank works
The patch queue is ordered by points, up to 100, and every point is listed on its row. The points only order this list; they are not a CVSS score or the CyberView rating, which are shown in All CVEs. Points: known exploited per CISA 35 (or 15 if only rated high severity) · used by ransomware groups 10 · EPSS, the estimated chance of exploitation in 30 days, up to 15 · public exploit code 5 · internet-facing 10 · federal deadline passed 5, within 7 days 3 · you run an affected version 20, or you run the product and the version needs checking 10.
"Internet-facing" comes from the vendor advisory when a fix guide exists; otherwise it is a guess from the product name and is labelled as one. Version ranges come from NIST's NVD and can lag or be incomplete: treat "not affected" as a prompt to confirm against the vendor advisory, not as proof.
Look up one CVE
Type an id in the search box above, for example CVE-2024-3400, then press Enter or choose Look up. Only the one data file that holds it is loaded.
Browse
Nothing loaded yet.
Vendors in what is loaded
The most common vendors in the loaded CVEs. Choosing one sets the vendor filter.
How CyberView rates a vulnerability
Every CVE gets two answers, side by side: how severe it is (the CyberView rating, on the CVSS scale) and how urgent it is for you (the priority, CISA's own method). Both follow published standards, so a defender can defend them to their leadership and an auditor. The list is sorted by priority first, then by the CyberView rating, then by EPSS.
Priority: CISA's SSVC decision. Stakeholder-Specific Vulnerability Categorization gives one of four decisions from four questions: is it being exploited (CISA's Known Exploited Vulnerabilities catalog or CISA's own assessment), can an attacker automate it, does it give total or partial control, and how much the affected system matters to your mission and to people's well-being. CISA recommends fixing Act as soon as possible, Attend sooner than your standard update timelines, and Track* and Track within standard update timelines (Track* is watched more closely). The decision table is CISA's own, as published by CERT/CC. Where CISA has not assessed a CVE, automation and impact are estimated from the CVSS vector and labelled as estimates. Mission impact is yours to set; the default is medium. When the CVE record's own description says exploitation was observed, or that exploit code is public, and CISA's assessment says less, the rating uses the description and labels it as the assigner's statement. The same goes for the vendor's own security advisory (Microsoft, Cisco, Fortinet, Palo Alto Networks, Red Hat, Ubuntu, Debian, Oracle, Google Chrome, Apple, Mozilla, Ivanti): when it says the flaw is exploited in the wild, the CVE shows a link to it with the vendor's own words, labelled as the vendor's statement.
Fix by: CISA BOD 26-04 Table 1. Binding Operational Directive 26-04 (June 2026), which replaced BOD 22-01, sets remediation timelines from whether the system is publicly exposed, whether the flaw is in the KEV catalog, whether exploitation can be automated and the technical impact: 3 days (with forensic triage when a known-exploited flaw gives total control), 14 days, 60 days, or at the next scheduled upgrade. It binds US federal civilian agencies; CyberView shows it as the current government benchmark for everyone. A flaw in the KEV catalog is never rated below what this table demands of it: Attend when the timeline is 14 days, Act when it is 3 days. Set whether your system is internet-facing to see one timeline instead of both.
The CyberView rating: CVSS, adjusted for exploitation. It starts from the CVSS base score (the assigner's or CISA's, otherwise NVD's, with the version named) and applies CVSS's own Exploit Code Maturity metric, the way CVSS v3.1's temporal score does (FIRST CVSS v3.1 specification, sections 3.1 and 7.2): High x 1.00 when the flaw is exploited in the wild (CISA's KEV catalog, CISA reports active exploitation, the vendor's own advisory says so, or the CVE record says so), Proof-of-Concept x 0.94 when exploit code is public, Unproven x 0.91 when no exploitation or public exploit is reported. The result is rounded up to one decimal with CVSS's Roundup. The scale (0.0 to 10.0) and the bands are exactly CVSS's: None 0.0, Low 0.1 to 3.9, Medium 4.0 to 6.9, High 7.0 to 8.9, Critical 9.0 to 10.0. So a CVSS 9.8 flaw on CISA's KEV catalog stays 9.8 Critical; with only a public proof of concept it is 9.3 Critical; with no exploitation seen it is 9.0 Critical; a CVSS 7.5 flaw nobody exploits yet is 6.9 Medium. It can be lower than CVSS because nothing shows attackers using the flaw yet, and it is never higher; it returns to the CVSS score as soon as exploitation is reported. A CVE with no CVSS score is shown as not scored, never given an invented number. Every CVE lists each step: the base score and its source, the Exploit Code Maturity value and why, and the result. EPSS, ransomware use, CISA's dates and your own settings are not part of it; they are shown with the priority, which is what says how urgent a flaw is.
Supporting signals, never the rating on their own. CVSS measures how severe a flaw is in general, not how urgent it is for you. EPSS estimates the chance of exploitation in the next 30 days; FIRST advises using it alongside CVSS and the KEV catalog and never multiplying the two. CyberView's one addition to CISA's table: a flaw with no exploitation yet that EPSS puts in the top 5% moves from Track to Track*. Ransomware use comes from CISA's catalog.
Other benchmarks. The UK NCSC's "update by default" policy asks for internet-facing services to be updated within 5 days, operating systems and applications within 7 and internal systems within 14, whatever the severity. NIST SP 800-40 Rev. 4 sets no fixed number of days; it asks each organisation to set its own timelines by risk.
Rejected CVEs are IDs the CVE Program withdrew: duplicates, reports found not to be vulnerabilities, or IDs reserved and never used. They are kept for completeness (NVD lists the same 19,000 or so) and are never rated.
Sources: CISA SSVC · CERT/CC SSVC decision tables · CISA BOD 26-04 · CISA KEV catalog · FIRST CVSS v3.1 specification · FIRST: using EPSS · NCSC update by default · NIST SP 800-40 Rev. 4
Your software list
It is read and matched here, in this browser, and saved only on this device. Nothing is uploaded. Clear it at any time.
Nothing loaded yet
Scan your own network: the CyberView Scanner
Only scan systems you own, or systems whose owner has given you written permission to test. Scanning other people's systems without permission may be unlawful. The scanner will not start until you list your targets in a scope file and attest there that you are authorized; it prints your attestation and scope at the start of every run and writes them into the report.
A command-line tool (Node.js 22, nothing to install) that finds the software your servers announce (SSH banners, web server headers, mail greetings, TLS certificates, and optional read-only DNS, NTP and SNMP service checks), matches the versions against the known-exploited flaws and ranges on this page, and ranks what to patch first by the CyberView rating, listing every point, with the fix and how sure it is. It writes JSON, CSV, SARIF and a software list this view can import. It can find the hosts for you within the scope you attest to — sweep your ranges, resolve and expand your own domains from Certificate Transparency, import an asset list, or read your own read-only cloud inventory — and scan every TCP port on your own private ranges.
Detection only: it never exploits anything, logs in, tests passwords or SNMP community strings, floods or hides what it is. It names itself in its requests and SSH identification, sends only a benign version or banner probe (a TLS handshake, and a single standard query for each UDP check), keeps to polite limits you can lower but not raise, re-checks every host it discovers against your scope, needs an extra confirmation for any public address and keeps a hard cap on how much public space it will touch, never runs your cloud CLI or reads your keys, and never uploads your results. It can run offline from a downloaded copy of CyberView's data, for networks with no internet access. No AI model runs in it.
A proprietary CyberView product, free to download and use on your own authorised systems under its licence; no redistribution without permission.
Patching closes the hole; hunting checks whether someone came through it first. One card for each flaw being exploited and each reported campaign, most urgent first: what the vendor says to look for, where to look in your logs, and the detection rules and indicator files the publishers released. CyberView links to those files and never copies indicators, so you always get the publisher's current version.
How this list is ranked
Rank points only order this list; they are not a CVSS score or the CyberView rating, and every point is listed on the row. Points: known exploited (a CVE the advisory names is in CISA's KEV catalog) 40, or exploited as the advisory states 30, or public exploit code as the advisory states 10 · CVSS 9.0 or higher 25, 7.0 to 8.9 15, 4.0 to 6.9 5 (the highest base score in the advisory) · deployed in a lifeline sector named by CISA (energy, water, healthcare, transportation, communications and others) 10 · no vendor fix for at least one product 5 · names a product on your software list 20 · published in the last 14 days 5. At most 100. An advisory in which the vendor states its products are not affected gets no points.
Mitigations and fixes are in each advisory, linked on its row, written by CISA or by the vendor itself: CyberView does not rewrite them. The software list match is by product name only and runs in this browser.