Skip to content

Commit d083756

Browse files
rrobergerlxdev
andauthored
11/12/25 release branch (#3759)
* #3758 Update Metrics page * #3757 Remove outage banner, update faq, & add news article for CVE List search upgrade --------- Co-authored-by: Roy Lane <[email protected]>
1 parent aa91016 commit d083756

File tree

4 files changed

+63
-25
lines changed

4 files changed

+63
-25
lines changed

src/assets/data/NotificationBanner.json

Lines changed: 0 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -28,26 +28,6 @@
2828
{
2929
"contentType": "paragraph",
3030
"content": "."
31-
},
32-
{
33-
"contentType": "paragraph",
34-
"content": "<br/><br/>"
35-
},
36-
37-
{
38-
"contentType": "paragraph",
39-
"content": "<b>NOTICE &mdash;</b>"
40-
},
41-
42-
{
43-
"contentType": "internalLink",
44-
"link": "/",
45-
"linkText": "CVE List Search"
46-
},
47-
48-
{
49-
"contentType": "paragraph",
50-
"content": "on this CVE.ORG website will be <strong>unavailable on November 12, 2025, between 10:00 AM and 12:00 PM EDT</strong> so that the capability can be upgraded. As a result, searching CVE IDs and CVE Records will be unavailable during this time. We apologize for the inconvenience and thank you for your understanding."
5131
}
5232
]
5333
}

src/assets/data/faqs.json

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -270,14 +270,15 @@
270270
"questionId": "search_cve",
271271
"questionText": "How do I search the CVE List",
272272
"questionResponseParagraphs": [
273-
"You may search using:<br/><ul><li><strong>IDs</strong><ul><li>CVE ID<ul><li>Specific <a href='/ResourcesSupport/Glossary?activeTerm=glossaryCVEID'>CVE ID</a> (e.g., “CVE-2015-8405”)</li><li>Note that this returns records where there is a match for the CVE ID anywhere in the CVE Record (e.g., “CVE-2015-8405” returns the CVE named, as well as any CVEs that have that CVE ID in other fields, such as in the description)</li><li>The nominal CVE ID Year (e.g., “CVE-2025” returns all CVEs reserved in the CVE-2025 year series)</li><li>The year must be a full year (e.g., “CVE-202” is invalid and will produce no results)</li></ul></li><li>CWE ID<ul><li>Specific <a href='/About/RelatedEfforts#CWE'>Common Weakness Enumeration (CWE&trade;)</a> entries (e.g., “CWE-123”)</li></ul></li><li> CAPEC ID<ul><li>Specific <a href='/About/RelatedEfforts#CAPEC'>Common Attack Pattern Enumerations and Classification (CAPEC&trade;)</a> entries (e.g., “CAPEC-123”)</li></ul></li></ul></li><li><strong>General</strong><ul><li>Note that if you provide multiple CVE IDs, the search will only return results that contain ALL CVE IDs you specify in each record, which may not be what you expect</li><li>Search terms are case-insensitive and may contain words of alphanumeric and Unicode characters</li><li>The wildcard characters “*” and “?” are now supported, which allows searching for patterns instead of only exact matches. For example, searching for “vuln*” would return any CVE Records that contains the word “vulnerable” or “vulnerability”, as well as any other word that starts with “vuln”. The “?” is similar but matches only a single character, useful for finding slight variations in how a word is spelled. Including the “?” will match any letter, number, or symbol in the position in which it is placed. For example, searching for “reject??” would return any CVE Records that include “reject” followed by any other two characters (i.e., letters, numbers, or symbols) such as “rejected”, “rejector”, “reject61”, etc.</li><li>Supported search scenarios include:<br/><ul><li>Wildcards (e.g., “vuln*”, “reject??”)</li><li>Hyphenated words (e.g., “man-in-the-middle”)</li><li>Exact version strings (e.g., “6.17.4”)<li>Exact IPv4 strings (e.g., “127.0.0.1”)</li><li>Exact filenames (e.g., “main.cpp”)</li><li>URLs (e.g., “http://www.ibm.com/support/docview.wss?uid”)</li></ul></li><li>Symbols currently not supported are:\u00a0\u00a0\u00a0() {} [] \" ' ` &lt;&gt; | ; ! ~ ^ + %</li></ul></li></ul>"
274-
]
273+
"You may search using:<br><ul><li><strong>IDs</strong><ul><li>CVE ID <ul><li>Specific <a href='/ResourcesSupport/Glossary?activeTerm=glossaryCVEID'>CVE ID</a> (e.g., “CVE-2015-8405”)</li><li>Note that this returns records where there is a match for the CVE ID anywhere in the CVE Record (e.g., “CVE-2015-8405” returns the CVE named, as well as any CVEs that have that CVE ID in other fields, such as in the description)</li></ul></li><li>CWE ID <ul><li>Specific <a href='/About/RelatedEfforts#CWE'>Common Weakness Enumeration (CWE&trade;)</a> entries (e.g., “CWE-123”)</li></ul></li><li>CAPEC ID <ul><li>Specific <a href='/About/RelatedEfforts#CAPEC'>Common Attack Pattern Enumerations and Classification (CAPEC&trade;)</a> entries (e.g., “CAPEC-123”)</li></ul></li></ul></li></ul><ul><li><strong>Date and Date Range Search</strong><ul><li>you can perform date searches on date fields, using the following formats <ul><li>YYYY-MM-DD (e.g., 2025-10-28)</li><li>YYYY-MM-DDTHH:MM:SS (e.g., 2025-10-28T12:00:00-4:00 for noon on that date New York time)</li></ul></li><li>you can perform date range searches by separating a beginning date/time and the ending date/time with 2 periods <ul><li>YYYY-MM-DD..YYYY-MM-DD (e.g., 2025-10-27..2025-10-28 for the 48 hour period between those 2 dates)</li><li>YYYY-MM-DDTHH:MM:SS..YYYY-MM-DDTHH:MM:SS (e.g., 2025-10-28T01:30:00..2025-10-28T01:45:00 for the 15 minute period between those 2 timestamps)</li></ul></li><li>If you don't specify a time zone, the \"Z\" time zone is assumed (i.e., Greenwich Mean Time)</li><li>date ranges are inclusive, meaning the search will include both the starting date and the ending date in the results</li></ul></li></ul><ul><li><strong>Exact Phrase Search</strong><ul><li>surround the phrase in double quotes (e.g., \"access denied\")</li><li>you can mix and match phrases and words (e.g., \"access denied\" vuln*)</li></ul></li></ul><ul><li><strong>General</strong><ul><li>Note that if you provide multiple CVE IDs, the search will only return results that contain ALL CVE IDs you specify in each record, which may not be what you expect</li><li>Note that currently you cannot mix text search with date/range search, you can only search on one or the other</li><li>Search terms are case-insensitive and may contain words of alphanumeric and Unicode characters</li><li>The wildcard characters “*” and “?” are now supported, which allows searching for patterns instead of only exact matches. For example, searching for “vuln*” would return any CVE Records that contains the word “vulnerable” or “vulnerability”, as well as any other word that starts with “vuln”. The “?” is similar but matches only a single character, useful for finding slight variations in how a word is spelled. Including the “?” will match any letter, number, or symbol in the position in which it is placed. For example, searching for “reject??” would return any CVE Records that include “reject” followed by any other two characters (i.e., letters, numbers, or symbols) such as “rejected”, “rejector”, “reject61”, etc.</li><li>Supported search scenarios include:<br><ul><li>Wildcards (e.g., “vuln*”, “reject??”)</li><li>Hyphenated words (e.g., “man-in-the-middle”)</li><li>Exact version strings (e.g., “6.17.4”) <li>Exact IPv4 strings (e.g., “127.0.0.1”)</li><li>Date (e.g., YYYY-MM-DD [e.g., 2025-11-12] or YYYY-MM-DDTHH:MM:SS [e.g., 2025-11-28T12:00:00-4:00])</li><li>Date range (e.g., YYYY-MM-DD..YYYY [e.g., 2025-11-12..2025-11-28] or YYYY-MM-DDTHH:MM:SS..YYYY-MM-DDTHH:MM:SS [e.g., 2025-10-28T01:30:00..2025-10-28T01:45:00])</li><li>Exact phrase (e.g., “access denied”)</li><li>Exact filenames (e.g., “main.cpp”)</li><li>URLs (e.g., “http://www.ibm.com/support/docview.wss?uid”)</li></ul></li><li>Symbols currently not supported are:\u00a0\u00a0\u00a0() {} [] ' ` &lt;&gt; | ; ! ~ ^ + %</li></ul></li></ul>"
274+
]
275275
},
276276
{
277277
"questionId": "search_cve_and",
278278
"questionText": "In the search box on CVE.ORG, what CVE Record fields are searched",
279279
"questionResponseParagraphs": [
280-
"All CVE Record fields are searched when using the search box on CVE.ORG. However, if the search comprises more than one keyword, all keywords must be present in a given field for the record to be returned."
280+
"For text searches, all CVE Record fields are searched when using the search box on CVE.ORG. However, if the search comprises more than one keyword, all keywords must be present in a given field for the record to be returned.",
281+
"For date and date range searches, only standard CVE date fields defined in the schema (e.g., date updated) are searched."
281282
]
282283
},
283284
{

src/assets/data/metrics.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -832,11 +832,11 @@
832832
"data": [
833833
{
834834
"heading": "All CNAs",
835-
"percentage": "87"
835+
"percentage": "85"
836836
},
837837
{
838838
"heading": "CNA-LRs",
839-
"percentage": "13"
839+
"percentage": "15"
840840
}
841841
]
842842
},

src/assets/data/news.json

Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,62 @@
11
{
22
"currentNews": [
3+
{
4+
"id": 599,
5+
"newsType": "news",
6+
"title": "Searching by Date and Exact Phrases Now Available in “CVE List Keyword Search” on CVE.ORG Website",
7+
"urlKeywords": "CVE List Keyword Search Updated CVE ORG",
8+
"date": "2025-11-12",
9+
"description": [
10+
{
11+
"contentnewsType": "paragraph",
12+
"content": "“<a href='/'>CVE List Keyword Search</a>” on the CVE.ORG has been updated based upon feedback back from users. As a reminder, this search is for the CVE List only. It will only search <a href='/ResourcesSupport/Glossary?activeTerm=glossaryRecord'>CVE Records</a>. To search the overall website, use the “Site Search” located to the right of the CVE List search box above."
13+
},
14+
{
15+
"contentnewsType": "paragraph",
16+
"content": "This update to the CVE List Keyword Search adds support for date and date range searches and exact phrase searches, as follows:"
17+
},
18+
{
19+
"contentnewsType": "paragraph",
20+
"content": "<h4>Date and Date Range Search</h4>"
21+
},
22+
{
23+
"contentnewsType": "paragraph",
24+
"content": "CVE Records may now be searched by a specified date or a specified date range, in the following formats:"
25+
},
26+
{
27+
"contentnewsType": "paragraph",
28+
"content": "<ul><li><strong>Date Search format</strong><ul><li>YYYY-MM-DD (e.g., 2025-10-28)</li><li>YYYY-MM-DDTHH:MM:SS (e.g., 2025-10-28T12:00:00-4:00)</li></li></ul>"
29+
},
30+
{
31+
"contentnewsType": "paragraph",
32+
"content": "<ul><li><strong>Date Range Search format</strong><ul><li>YYYY-MM-DD..YYYY (e.g., 2025-10-27..2025-10-28)</li><li>YYYY-MM-DDTHH:MM:SS..YYYY-MM-DDTHH:MM:SS (e.g., 2025-10-28T01:30:00..2025-10-28T01:45:00)</li></li></ul>"
33+
},
34+
{
35+
"contentnewsType": "paragraph",
36+
"content": "<h4>Exact Phrase Search</h4>"
37+
},
38+
{
39+
"contentnewsType": "paragraph",
40+
"content": "CVE Records may now be searched using an exact phrase that is surrounded by double quotes. For example, searching for the phrase “access denied” would return CVE Records that contain the full phrase “access denied” and not CVE Records that contain those words separately."
41+
},
42+
{
43+
"contentnewsType": "paragraph",
44+
"content": "<ul><li><strong>Exact Phrase Search format</strong><ul><li>Surround the phrase in double quotes (e.g., “access denied”)</li></li></ul>"
45+
},
46+
{
47+
"contentnewsType": "paragraph",
48+
"content": "<h4>All CVE List Keyword Search Tips</h4>"
49+
},
50+
{
51+
"contentnewsType": "paragraph",
52+
"content": "View the complete list of CVE List keyword search tips <a href='/ResourcesSupport/FAQs#pc_cve_list_basicssearch_cve'>here</a>."
53+
},
54+
{
55+
"contentnewsType": "paragraph",
56+
"content": "We thank everyone who provided feedback, which continues to help us improve the capability for the community over time."
57+
}
58+
]
59+
},
360
{
461
"id": 598,
562
"newsType": "news",

0 commit comments

Comments
 (0)