mirror of
https://github.com/0xMarcio/cve.git
synced 2026-10-27 16:51:03 +00:00
Sync CVE metadata 2026-09-09
This commit is contained in:
CVE-BOT committed
1 parent
8b9d3bdbe4
commit
8f6945a04c
54 files changed
+812
-17
No files matched your search
@@ -1,8 +1,8 @@
|
||||
<div align="center">
|
||||
|
||||
<a href="https://pocindex.io/"><img src="https://raw.githubusercontent.com/0xMarcio/pocindex/main/docs/hero.svg?v=171489-82728-1186" alt="PoC Index" width="100%"></a>
|
||||
<a href="https://pocindex.io/"><img src="https://raw.githubusercontent.com/0xMarcio/pocindex/main/docs/hero.svg?v=171529-82768-1186" alt="PoC Index" width="100%"></a>
|
||||
|
||||
[](https://github.com/0xMarcio/pocindex/commits/main) [](https://github.com/0xMarcio/pocindex/actions/workflows/hot_cves.yml) [](https://pocindex.io/) [](https://pocindex.io/) [](https://github.com/0xMarcio/pocindex/stargazers)
|
||||
[](https://github.com/0xMarcio/pocindex/commits/main) [](https://github.com/0xMarcio/pocindex/actions/workflows/hot_cves.yml) [](https://pocindex.io/) [](https://pocindex.io/) [](https://github.com/0xMarcio/pocindex/stargazers)
|
||||
|
||||
<a href="https://pocindex.io/"><img src="https://raw.githubusercontent.com/0xMarcio/pocindex/8dec6181e823d641132e0ee8a52a1612c2b5dd37/docs/search.svg" alt="Search PoC Index" width="100%"></a>
|
||||
|
||||
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-12259](https://www.cve.org/CVERecord?id=CVE-2026-12259)
|
||||
**Improper Input Validation in nltk/nltk**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
In nltk version 3.9.4, the `nltk.downloader.Downloader._download_package()` function writes downloaded package bytes to disk and may extract them before enforcing SHA-256 or MD5 checksum validation. This allows an attacker to tamper with the package response body for `info.url` through a compromised mirror, malicious proxy, or other source-substitution condition, leading to the installation of attacker-controlled package bytes. The vulnerability can result in malicious corpus or model content being trusted by downstream users or applications.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-5wp5-5229-5g6q
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -15,6 +15,7 @@ In ONNX before 1.21.0, the 'save_external_data' function builds the external-dat
|
||||
|
||||
#### Reference
|
||||
- https://github.com/onnx/onnx/security/advisories/GHSA-q56x-g2fj-4rj6
|
||||
- https://github.com/advisories/GHSA-q56x-g2fj-4rj6
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -12,7 +12,7 @@ Gitea before 1.27.1 allows remote code execution via the diffpatch API through G
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
No PoCs from references.
|
||||
- https://github.com/advisories/GHSA-rcr6-4jqh-j84m
|
||||
|
||||
#### Github
|
||||
- https://github.com/HORKimhab/CVE-2026-60004
|
||||
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-62383](https://www.cve.org/CVERecord?id=CVE-2026-62383)
|
||||
**nltk IPIPANCorpusReader Symlink Arbitrary File Read**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
nltk versions before 3.10.2 contain a symlink-based arbitrary file read vulnerability in IPIPANCorpusReader methods that bypass nltk.pathsec validation entirely. Attackers can place a symlink in the corpus root directory and read arbitrary files accessible to the process by calling channels(), domains(), categories(), or fileids() methods with the symlink filename.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-3hhw-38pf-pxj6
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-62384](https://www.cve.org/CVERecord?id=CVE-2026-62384)
|
||||
**NLTK FramenetCorpusReader Symlink Sandbox Bypass before 3.10.2**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
NLTK versions before 3.10.2 contain a symlink-based sandbox bypass in FramenetCorpusReader that allows attackers to read arbitrary XML files outside the corpus root. Attackers can place symlinks with names containing no path separators inside the corpus subdirectory, which pass the path validation guard and are resolved to files outside the intended corpus root when accessed via frame_by_name(), _lu_file(), or doc() methods.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-f833-7jw8-xwrv
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-62385](https://www.cve.org/CVERecord?id=CVE-2026-62385)
|
||||
**NLTK 3.9.4 Path Traversal via FrameNet and NKJP Readers**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
NLTK versions before 3.10.0 contain a path traversal vulnerability in FramenetCorpusReader and NKJPCorpusReader that allows attackers to parse XML files outside the corpus root by supplying unsafe selectors or poisoned index state. Attackers can exploit frame_by_name, doc, lu, and header methods with crafted parameters to read arbitrary XML files accessible to the application.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-568f-pv23-39p4
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-65915](https://www.cve.org/CVERecord?id=CVE-2026-65915)
|
||||
**NLTK before 3.10.0 Arbitrary File Read via FileSystemPathPointer**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
NLTK versions before 3.10.0 contain a logic bug in FileSystemPathPointer.open() where the sandbox validation check compares a normalized path against itself, making the security check permanently inert. Attackers can pass file:// URLs to nltk.data.load() to read arbitrary files accessible to the process user, including credentials and configuration files.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-72r2-7mfr-5xr9
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,19 @@
|
||||
### [CVE-2026-67321](https://www.cve.org/CVERecord?id=CVE-2026-67321)
|
||||
**axios 0.31.1 before 0.33.0 and 1.15.1 before 1.18.0 Denial of Service via maxDepth bypass**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
axios versions 0.31.1 before 0.33.0 and 1.15.1 before 1.18.0 contain an incomplete depth-limit bypass in toFormData.js when serializing objects with top-level keys ending in '{}'. Attackers who control object keys and nested values passed to axios form or parameter serialization can trigger a RangeError from JSON.stringify, causing denial of service in the affected request path.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-hcpx-6fm6-wx23
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-67322](https://www.cve.org/CVERecord?id=CVE-2026-67322)
|
||||
**GitPython before 3.1.52 Environment Variable Exfiltration via clone_from**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
GitPython before 3.1.52 is vulnerable to environment-variable exfiltration in Repo.clone_from(). The caller-supplied remote URL is passed through Git.polish_url(), which on non-Cygwin platforms calls os.path.expandvars() on the URL before invoking git clone. An attacker who controls the clone URL can embed $NAME or ${NAME} tokens that are expanded to the values of the hosting process's environment variables (e.g., AWS_SECRET_ACCESS_KEY or GITHUB_TOKEN). The resulting URL, now containing the secret, is transmitted over the network to an attacker-controlled host during the clone attempt, disclosing the secret.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-rwj8-pgh3-r573
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-67323](https://www.cve.org/CVERecord?id=CVE-2026-67323)
|
||||
**GitPython before 3.1.51 Command Injection via unguarded Git options**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
GitPython before 3.1.51 fails to guard against dangerous Git options passed as keyword arguments in Repo.archive() and git.ls_remote(), allowing command injection via options such as --exec/--upload-pack (leading to arbitrary command execution). Additionally, Repo.iter_commits() and Repo.blame() do not check for leading-dash revision arguments, so a revision like --output=<path> can cause Git to open and truncate an arbitrary file. Exploitation requires an application that passes attacker-controlled arguments to these methods.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-956x-8gvw-wg5v
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-68584](https://www.cve.org/CVERecord?id=CVE-2026-68584)
|
||||
**SiYuan before v3.7.3 Authentication Bypass via Content Endpoints**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
SiYuan versions before v3.7.3 contain an authentication bypass vulnerability in publish mode where content-returning endpoints getHeadingChildrenDOM, getHeading*Transaction, and getBacklinkDoc perform no password check despite protecting the primary getDoc endpoint. Anonymous attackers can retrieve full content of password-protected documents by obtaining internal block IDs from reader-accessible endpoints and calling unprotected content endpoints to bypass the password gate.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-7j72-f6wg-cxw6
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-69222](https://www.cve.org/CVERecord?id=CVE-2026-69222)
|
||||
**LiquidJS: Uncontrolled Resource Consumption in `join` filter allows template authors to bypass `memoryLimit` and crash the process**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
LiquidJS is a Shopify / GitHub Pages compatible template engine in pure JavaScript. Prior to 10.27.2, the join filter in src/filters/array.ts computes complexity from array.length and separator length instead of the total string length produced by array.join(sep). The concat filter can cheaply double arrays of references, after which join materializes the referenced content while charging only for element count, allowing a template to exceed a configured memoryLimit by a large factor. The sibling array_to_sentence_string filter in src/filters/string.ts has the same accounting defect, and a crafted template can allocate toward V8's string or process memory limit and crash the process. This issue is fixed in version 10.27.2.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-4r6h-5v86-94p3
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-70626](https://www.cve.org/CVERecord?id=CVE-2026-70626)
|
||||
**NLTK before 3.9.4 Symlink Escape via CorpusReader**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
NLTK versions before 3.9.4 contain a symlink escape vulnerability in CorpusReader.open() that allows local attackers to read arbitrary files outside the corpus root. The vulnerability exists because path validation is lexical and does not account for symlink resolution, enabling attackers to place symlinks inside the corpus root to access files outside the intended boundary.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-r6gq-whwq-mvg9
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-72789](https://www.cve.org/CVERecord?id=CVE-2026-72789)
|
||||
**SiYuan before v3.7.4 Authentication Bypass via Encrypted Notebooks**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
SiYuan before v3.7.4 fails to properly validate publish access for encrypted notebooks, treating them as publicly accessible by default. Anonymous readers can enumerate and retrieve fully decrypted document content from unlocked encrypted notebooks through the publish API without authentication or key material.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-v684-q882-jgmq
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-72790](https://www.cve.org/CVERecord?id=CVE-2026-72790)
|
||||
**SiYuan before v3.7.4 Information Disclosure via getNotebookInfo**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
SiYuan before v3.7.4 contains an information disclosure vulnerability in the /api/notebook/getNotebookInfo endpoint that returns notebook metadata without authorization checks. Attackers can read notebook names, document counts, sizes, and timestamps for closed or non-published notebooks that should be hidden from readers.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-74pj-6g7r-j55c
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-73087](https://www.cve.org/CVERecord?id=CVE-2026-73087)
|
||||
**Dozzle: SSRF guard bypass via IPv6 transition addresses (6to4/NAT64/Teredo) in webhook notification dispatcher**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
Dozzle is a realtime log viewer for docker containers. From 10.5.2 until 10.6.15, the isBlockedIP SSRF guard in internal/notification/dispatcher/webhook.go, used by safeDialContext for webhook notification URLs, does not inspect IPv4 addresses embedded in 6to4, NAT64, Teredo, or IPv4-compatible IPv6 addresses, allowing an authenticated user to reach loopback or link-local targets that the guard intends to block. This issue is fixed in version 10.6.15.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-p2w3-6x73-2f6x
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-73262](https://www.cve.org/CVERecord?id=CVE-2026-73262)
|
||||
**Prowler: Stored XSS in HTML reports through unescaped cloud resource tags**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
Prowler is a cloud security platform. Prior to 5.37.0, Prowler's HTML output formatter in prowler/lib/outputs/html/html.py inserted finding.resource_tags, assembled by unroll_dict and parse_html_string, into generated reports without HTML escaping, allowing a cloud principal who can modify a scanned resource tag to store HTML or JavaScript that executes when another user opens the report. This issue is fixed in version 5.37.0.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-c2jg-2778-ggm4
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,19 @@
|
||||
### [CVE-2026-75596](https://www.cve.org/CVERecord?id=CVE-2026-75596)
|
||||
**Netty: Fragmented ClientHello records trigger quadratic pre-handshake reassembly in default SNI parsing**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
Netty is an asynchronous, event-driven network application framework. Prior to 4.1.137.Final and 4.2.17.Final, the default io.netty.handler.ssl.SniHandler constructors use the pre-handshake ClientHello aggregation path in handler/src/main/java/io/netty/handler/ssl/SslClientHelloHandler.java at io.netty.handler.ssl.SslClientHelloHandler#decode, where handshakeBuffer.clear() and writeBytes() recopy all previously received body bytes for every additional TLS record. An unauthenticated remote peer can advertise a large ClientHello and deliver its body in thousands of tiny records, causing quadratic CPU work on the event loop before the TLS handshake completes and degrading TLS handling for other clients. This issue is fixed in versions 4.1.137.Final and 4.2.17.Final.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-fccg-mwvh-qqg4
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-76217](https://www.cve.org/CVERecord?id=CVE-2026-76217)
|
||||
**GitPython before 3.1.58 Arbitrary File Read via pathspec-from-file**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
GitPython versions before 3.1.58 fail to validate options passed to git rm and git checkout commands in IndexFile.remove() and Head.checkout(). Attackers can supply --pathspec-from-file and --pathspec-file-nul parameters to read arbitrary files accessible to the process, with full file contents returned in GitCommandError.stderr.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-hh9p-6wh2-4mfc
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-76220](https://www.cve.org/CVERecord?id=CVE-2026-76220)
|
||||
**GitPython before 3.1.58 Command Execution via split_single_char_options**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
GitPython before 3.1.58 contains a command execution vulnerability in the check_unsafe_options guard that can be bypassed by combining a single-character kwarg with split_single_char_options=False. Attackers can supply a crafted kwargs dictionary to guarded methods like clone_from to emit a joined token parsed as --upload-pack, enabling arbitrary OS command execution at default allow_unsafe_options=False.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-wvpp-8hx9-p66j
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-76222](https://www.cve.org/CVERecord?id=CVE-2026-76222)
|
||||
**GitPython before 3.1.58 Path Traversal via .gitmodules Submodule Name**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
GitPython before 3.1.58 fails to validate submodule names from .gitmodules files, allowing attackers to create Git repositories at arbitrary filesystem paths outside the intended clone directory. Attackers can craft malicious repositories with traversal sequences in submodule names that GitPython processes during submodule initialization, creating attacker-controlled Git repositories at escaped filesystem locations.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-hmq2-w58f-27jc
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-78675](https://www.cve.org/CVERecord?id=CVE-2026-78675)
|
||||
**GitPython before 3.1.59 Local File Content Disclosure via .gitmodules**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
GitPython before 3.1.59 fails to disable merge_includes when parsing .gitmodules, allowing attackers to disclose local file content by including arbitrary file paths via [include] directives. Attackers can craft a malicious .gitmodules file with include directives pointing to sensitive files; when repo.submodules is accessed, GitConfigParser raises MissingSectionHeaderError embedding the target file's first line verbatim in the exception message.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-7833-fr7j-v32q
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-78676](https://www.cve.org/CVERecord?id=CVE-2026-78676)
|
||||
**GitPython before 3.1.59 Remote Code Execution via Config Injection**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
GitPython before 3.1.59 fails to safely re-serialize multi-line git-config values during write operations, corrupting dormant quoted values into injected directives like core.hooksPath. Attackers can craft config files with embedded newlines that become live git directives after any unrelated GitPython config write, enabling arbitrary code execution via hook invocation.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-284h-m62q-gf8w
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-78677](https://www.cve.org/CVERecord?id=CVE-2026-78677)
|
||||
**GitPython before 3.1.59 Path Traversal via separate-git-dir**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
GitPython before 3.1.59 omits --separate-git-dir from unsafe_git_clone_options, allowing attackers to create arbitrary git directories outside the intended clone destination. Attackers can pass a separate_git_dir parameter to Repo.clone_from() or Repo.clone() to redirect repository metadata to an attacker-controlled filesystem path, enabling arbitrary directory creation and potential hook execution.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-8mcc-hrx5-hvxc
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-78682](https://www.cve.org/CVERecord?id=CVE-2026-78682)
|
||||
**NLTK before 3.10.3 SSRF Protection Bypass via Proxy**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
NLTK before 3.10.3 contains a server-side request forgery vulnerability in nltk.pathsec.urlopen (and callers nltk.data.load, nltk.downloader.Downloader.index/download) when an HTTP proxy is configured. pathsec.urlopen validates the requested hostname locally, but proxy-handler inheritance disables the safe HTTP/HTTPS handlers so the actual fetch is performed by the proxy against a destination that is never re-validated. An attacker can supply a validated public URL that the proxy forwards to an internal loopback-only service, allowing disclosure of internal HTTP resources, loading of forged downloader indexes, and installation of attacker-chosen package content.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-6ww7-3frv-cqxh
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-78683](https://www.cve.org/CVERecord?id=CVE-2026-78683)
|
||||
**NLTK before 3.10.0 Remote Code Execution via Unsafe Pickle Deserialization**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
NLTK before 3.10.0 (affected versions <=3.9.4) contains an unsafe pickle deserialization vulnerability in the TransitionParser.parse() method (nltk/parse/transitionparser.py). The method calls pickle_load() with the default restricted=False, routing deserialization through WarningUnpickler, which does not override find_class() and therefore permits arbitrary class resolution. When an application loads an attacker-crafted model file, embedded pickle gadget chains execute arbitrary Python code with the privileges of the user running the application. NLTK provides a RestrictedUnpickler for safe deserialization, but it is not used by production code paths. Fixed in 3.10.0.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-rhp5-r9x4-f5g2
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-79657](https://www.cve.org/CVERecord?id=CVE-2026-79657)
|
||||
**NLTK before 3.10.3 Remote Code Execution via Unsafe Pickle Deserialization**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
NLTK versions before 3.10.3 contain a remote code execution vulnerability in allowlisted pickle loaders that trust entire module namespaces instead of specific safe callables. Attackers can craft malicious pickle payloads invoking dangerous in-namespace functions like ReppTokenizer._execute and numpy.f2py.crackfortran.myeval through pickle REDUCE to execute arbitrary commands during model or tokenizer artifact loading.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-x99w-6fgc-pmfw
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-79674](https://www.cve.org/CVERecord?id=CVE-2026-79674)
|
||||
**NLTK 3.10.2 Path Traversal via corpus-reader constructors**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
NLTK versions before 3.10.3 contain a path sandbox bypass vulnerability in corpus-reader constructors that allows attackers to read files outside the intended data root. Attackers can supply arbitrary corpus root paths to LinThesaurusCorpusReader and PanLexLiteCorpusReader constructors to access filesystem content and SQLite databases outside the pathsec sandbox boundary.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-3gq4-3j92-5w49
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-79676](https://www.cve.org/CVERecord?id=CVE-2026-79676)
|
||||
**NLTK before 3.10.3 Path Traversal via Symlink Bypass**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
NLTK versions before 3.10.3 contain a path traversal vulnerability in corpus readers that reopen root-derived paths using built-in open() instead of nltk.pathsec.open(), allowing symlinks to escape trusted roots. Attackers who stage symlinked corpus files under a trusted data root can disclose outside-root content through normal corpus reader methods like channels(), domains(), and synonyms().
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-p4rw-rvv2-7xwr
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-81725](https://www.cve.org/CVERecord?id=CVE-2026-81725)
|
||||
**NLTK before 3.10.3 Regular Expression Denial of Service via Pl196xCorpusReader**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
NLTK before 3.10.3 contains a regular expression denial of service vulnerability in Pl196xCorpusReader that allows attackers to cause quadratic CPU consumption by supplying malformed TEI blocks with many unmatched opening tags. Attackers can exploit lazy regex patterns in the read_block method through public APIs like words() and tagged_words() to force repeated rescans and achieve near-quadratic runtime growth.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-8mpw-7fpc-4gqj
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,21 @@
|
||||
### [CVE-2026-83605](https://www.cve.org/CVERecord?id=CVE-2026-83605)
|
||||
**xmldom: Attribute name injection via setAttribute() bypasses requireWellFormed**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. Prior to @xmldom/xmldom versions 0.8.14 and 0.9.11, and in xmldom version 0.6.0 and earlier, Element.setAttribute() calls the private _createAttribute(name) path without validating the attribute name, while Document.createAttribute(name) validates against QName. XMLSerializer.serializeToString() emits attribute names verbatim, and requireWellFormed: true did not validate them, so a crafted name can terminate the intended attribute and inject additional attributes, including event handlers, into browser-consumed output; synthesized xmlns:PREFIX declarations expose the same unchecked-name boundary. This issue is fixed in @xmldom/xmldom versions 0.8.14 and 0.9.11; no fixed version is available for xmldom.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-4w3w-2rp5-g8jm
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,20 @@
|
||||
### [CVE-2026-83606](https://www.cve.org/CVERecord?id=CVE-2026-83606)
|
||||
**xmldom PI grammar regex ReDoS: quadratic backtracking on unterminated processing instructions**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. From 0.9.0-beta.9 until 0.9.11, the processing-instruction production in lib/grammar.js lets the greedy S+ separator and lazy Char*? data group repeatedly repartition a long whitespace tail when the required closing ?> is absent. Both parsePI and parseProcessingInstruction apply the expression to the entire remaining source, causing quadratic backtracking during DOMParser.parseFromString() under default options and allowing a small unauthenticated XML input to stall the Node.js event loop. This issue is fixed in @xmldom/xmldom version 0.9.11.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-g53g-w8rj-fmg7
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,21 @@
|
||||
### [CVE-2026-83607](https://www.cve.org/CVERecord?id=CVE-2026-83607)
|
||||
**xmldom: Element name injection via createElement() bypasses requireWellFormed**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. Prior to @xmldom/xmldom versions 0.8.14 and 0.9.11, and in xmldom version 0.6.0 and earlier, Document.createElement(tagName) stores an unvalidated element name and XMLSerializer.serializeToString() emits that name verbatim. The requireWellFormed: true path did not validate the element qualified name or synthesized xmlns:PREFIX declaration, so attacker-controlled tag names could inject attributes, elements, or processing instructions into serialized XML or HTML and could cause cross-site scripting when browser-consumed. The unchecked values violate the XML QName constraint, and default serialization and creation-time createElement() behavior remain permissive. This issue is fixed in @xmldom/xmldom versions 0.8.14 and 0.9.11; no fixed version is available for xmldom.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-w2rr-34g9-rvrj
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,21 @@
|
||||
### [CVE-2026-83608](https://www.cve.org/CVERecord?id=CVE-2026-83608)
|
||||
**xmldom: DocType `name` Injection Bypasses requireWellFormed**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. Prior to @xmldom/xmldom versions 0.8.15 and 0.9.12, and in xmldom version 0.6.0 and earlier, the DOCUMENT_TYPE_NODE branch in lib/dom.js validates publicId, systemId, and internalSubset under requireWellFormed: true but emits DocumentType.name verbatim. A name containing > or whitespace can terminate the <!DOCTYPE ...> declaration and inject sibling markup; the value can be supplied through createDocumentType() on the 0.8.x and unscoped lines or through a direct DocumentType.name property write on every affected line. The default path and legacy creation-time behavior remain permissive, while the vulnerable strict path fails to enforce an XML Name. This issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fixed version is available for xmldom.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-27p8-2357-5qqv
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,20 @@
|
||||
### [CVE-2026-83612](https://www.cve.org/CVERecord?id=CVE-2026-83612)
|
||||
**xmldom: HTML raw-text closing-tag case mismatch causes output amplification**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. From 0.9.0-beta.1 until 0.9.12, HTML-mode parsing through DOMParser.parseFromString() mishandles a mixed-case closing tag for the script, style, textarea, or title raw-text elements. parseHtmlSpecialContent, selected by isHTMLRawTextElement or isHTMLEscapableRawTextElement, uses a case-sensitive indexOf() and then calls substring() with a missing-close result of negative one, causing unstable parser progression and quadratic output amplification. A small untrusted text/html document can consequently consume disproportionate CPU and memory when parsed and serialized. This issue is fixed in @xmldom/xmldom version 0.9.12.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-6mj3-qw4j-hgrw
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,21 @@
|
||||
### [CVE-2026-83613](https://www.cve.org/CVERecord?id=CVE-2026-83613)
|
||||
**xmldom: Quadratic-time attribute deduplication**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. Prior to @xmldom/xmldom versions 0.8.15 and 0.9.12, and in xmldom version 0.6.0 and earlier, DOMHandler.startElement in lib/dom-parser.js inserts every parsed attribute through setAttributeNode, while NamedNodeMap.setNamedItem in lib/dom.js calls the linear getNamedItem or getNamedItemNS lookup for each insertion. A well-formed element with many distinct attributes therefore requires quadratic comparisons during DOMParser.parseFromString() and can stall a Node.js event loop before application validation. This issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fixed version is available for xmldom.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-8344-3jmq-59r6
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,22 @@
|
||||
### [CVE-2026-83614](https://www.cve.org/CVERecord?id=CVE-2026-83614)
|
||||
**xmldom: Quadratic-time parsing via the malformed-input recovery path — `parseElementStartPart` re-scan and `normalize()` adjacent-text merge**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. Prior to @xmldom/xmldom versions 0.8.15 and 0.9.12, and in xmldom versions 0.3.0 through 0.6.0, two independent quadratic paths can cause denial of service. In lib/sax.js, parseElementStartPart repeatedly rescans a malformed tag name to the next > during single-character recovery; in lib/dom.js, normalize() repeatedly removes and appends adjacent text nodes, causing quadratic reindexing and string rebuilding. The first path is reachable through default DOMParser.parseFromString() processing, while the second is also reachable through a direct normalize() call on a programmatically constructed DOM, and endDocument invokes that normalization after parsing. This issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fixed version is available for xmldom.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-93r5-fhx6-vmg9
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,21 @@
|
||||
### [CVE-2026-83615](https://www.cve.org/CVERecord?id=CVE-2026-83615)
|
||||
**xmldom: Quadratic-memory consumption**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. Prior to @xmldom/xmldom versions 0.8.15 and 0.9.12, and in xmldom versions 0.1.5 through 0.6.0, appendElement in lib/sax.js uses _copy to clone the complete currentNSMap for each nested element that declares a new namespace prefix. Keeping every ancestor map live on the parse stack creates quadratic peak namespace-map storage, so a small highly compressible XML document can exhaust the process heap before application validation. This issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fixed version is available for xmldom.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-965w-775f-mr7g
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,21 @@
|
||||
### [CVE-2026-83616](https://www.cve.org/CVERecord?id=CVE-2026-83616)
|
||||
**xmldom: Processing Instruction Target Injection Bypasses requireWellFormed**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. Prior to @xmldom/xmldom versions 0.8.15 and 0.9.12, and in xmldom version 0.6.0 and earlier, Document.createProcessingInstruction(target, data) in lib/dom.js accepts an unvalidated target, while the requireWellFormed: true serializer checks only for a colon and the reserved case-insensitive xml name on 0.9.x and performs no target check on 0.8.x. Because serialization emits <?target data?>, a target containing >, ?, whitespace, or another invalid XML-name character can break the processing-instruction boundary and inject XML structure. This issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fixed version is available for xmldom.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-c7q8-3ch8-vqpv
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,20 @@
|
||||
### [CVE-2026-83617](https://www.cve.org/CVERecord?id=CVE-2026-83617)
|
||||
**xmldom: requireWellFormed element/attribute name validation is bypassable via an embedded line terminator**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. From 0.9.11 until 0.9.12, the requireWellFormed: true element and attribute name checks use the anchored QName_exact expression produced by reg() in lib/grammar.js, which inherits the multiline flag. A name with a valid first line followed by U+000A, U+000D, U+2028, or U+2029 and breakout markup therefore passes validation and is emitted verbatim in element start and end tags or attribute names. This bypasses the strict-serialization checks introduced for the earlier element-name and attribute-name injection advisories, while the default serialization path remains outside the strict guarantee. This issue is fixed in @xmldom/xmldom version 0.9.12.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-jxjr-3g7g-3944
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,20 @@
|
||||
### [CVE-2026-83618](https://www.cve.org/CVERecord?id=CVE-2026-83618)
|
||||
**xmldom: requireWellFormed DocType publicId/systemId validation is bypassable via an embedded line terminator**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. From 0.9.10 until 0.9.12, the requireWellFormed: true serializer validates DocumentType.publicId and DocumentType.systemId with PubidLiteral_match and SystemLiteral_match expressions produced by reg() in lib/grammar.js, which inherit the multiline flag. A complete valid literal on the first line can therefore satisfy the matcher while U+000A, U+000D, U+2028, or U+2029 and breakout markup remain in the emitted <!DOCTYPE ...> declaration. This bypasses the strict-serialization mitigation for the earlier DocumentType injection advisory; creation and direct property assignment remain unvalidated by design. This issue is fixed in @xmldom/xmldom version 0.9.12.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-vr34-hp96-76pp
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
@@ -0,0 +1,18 @@
|
||||
### [CVE-2026-84372](https://www.cve.org/CVERecord?id=CVE-2026-84372)
|
||||
**Predis: Redis command injection and denial of service via CRLF smuggling in pipelined commands on aggregate connections**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
Predis is a flexible and feature-complete Redis and Valkey client for PHP. From version 3.0.0-RC1 until version 3.3.0, pipeline handling on aggregate cluster and replication connections reparses an already serialized RESP buffer in AbstractAggregateConnection::write() by splitting it with explode("\r\n") instead of honoring RESP length prefixes. Attacker-controlled keys or values containing CRLF sequences can therefore be interpreted by Command::deserializeCommand() as additional commands. On cluster connections, ClusterStrategy::getFakeKey() can route injected keyless commands using the literal fake key value "key", permitting operations such as shard-wide cache deletion, targeted data modification, data reads, or node disruption. On replication connections, malformed reparsing can throw an uncaught exception and repeatedly terminate affected requests. Only pipeline() reaches this vulnerable path; transaction() and MULTI are not affected. This issue is fixed in version 3.3.0.
|
||||
|
||||
### POC
|
||||
|
||||
#### Reference
|
||||
- https://github.com/advisories/GHSA-w6f5-v2h6-g786
|
||||
|
||||
#### Github
|
||||
No PoCs found on GitHub currently.
|
||||
+3
-3
@@ -1,5 +1,5 @@
|
||||
<svg xmlns="http://www.w3.org/2000/svg" width="1200" height="180" viewBox="0 0 1200 180"
|
||||
role="img" aria-label="PoC Index, 82,728 CVEs with public proof-of-concept exploits">
|
||||
role="img" aria-label="PoC Index, 82,768 CVEs with public proof-of-concept exploits">
|
||||
<clipPath id="card"><rect x="1" y="1" width="1198" height="178" rx="12"/></clipPath>
|
||||
<rect x="0.5" y="0.5" width="1199" height="179" rx="12" fill="#0d1117" stroke="#30363d"/>
|
||||
<g clip-path="url(#card)" opacity="0.6"><g>
|
||||
@@ -19,10 +19,10 @@
|
||||
<text x="56" y="132" font-family="ui-monospace,SFMono-Regular,Menlo,Consolas,monospace" font-size="15" fill="#2f81f7">pocindex.io</text>
|
||||
|
||||
<text x="620" y="96" font-family="ui-monospace,SFMono-Regular,Menlo,Consolas,monospace" font-size="34" font-weight="700"
|
||||
fill="#e6edf3" letter-spacing="-0.5">171,489</text>
|
||||
fill="#e6edf3" letter-spacing="-0.5">171,529</text>
|
||||
<text x="620" y="117" font-family="ui-monospace,SFMono-Regular,Menlo,Consolas,monospace" font-size="12"
|
||||
fill="#6e7681" letter-spacing="1.6">CVES INDEXED</text><text x="840" y="96" font-family="ui-monospace,SFMono-Regular,Menlo,Consolas,monospace" font-size="34" font-weight="700"
|
||||
fill="#2f81f7" letter-spacing="-0.5">82,728</text>
|
||||
fill="#2f81f7" letter-spacing="-0.5">82,768</text>
|
||||
<text x="840" y="117" font-family="ui-monospace,SFMono-Regular,Menlo,Consolas,monospace" font-size="12"
|
||||
fill="#6e7681" letter-spacing="1.6">WITH POCS</text><text x="1010" y="96" font-family="ui-monospace,SFMono-Regular,Menlo,Consolas,monospace" font-size="34" font-weight="700"
|
||||
fill="#f85149" letter-spacing="-0.5">1,186</text>
|
||||
|
||||
|
Before Width: | Height: | Size: 2.6 KiB After Width: | Height: | Size: 2.6 KiB |
@@ -20,10 +20,10 @@
|
||||
|
||||
<rect x="96" y="344" width="1088" height="1" fill="#30363d"/>
|
||||
<text x="96" y="430" font-family="ui-monospace,SFMono-Regular,Menlo,Consolas,monospace" font-size="46" font-weight="700"
|
||||
fill="#e6edf3" letter-spacing="-0.5">171,489</text>
|
||||
fill="#e6edf3" letter-spacing="-0.5">171,529</text>
|
||||
<text x="96" y="459" font-family="ui-monospace,SFMono-Regular,Menlo,Consolas,monospace" font-size="16"
|
||||
fill="#6e7681" letter-spacing="1.6">CVES INDEXED</text><text x="500" y="430" font-family="ui-monospace,SFMono-Regular,Menlo,Consolas,monospace" font-size="46" font-weight="700"
|
||||
fill="#2f81f7" letter-spacing="-0.5">82,728</text>
|
||||
fill="#2f81f7" letter-spacing="-0.5">82,768</text>
|
||||
<text x="500" y="459" font-family="ui-monospace,SFMono-Regular,Menlo,Consolas,monospace" font-size="16"
|
||||
fill="#6e7681" letter-spacing="1.6">WITH POCS</text><text x="880" y="430" font-family="ui-monospace,SFMono-Regular,Menlo,Consolas,monospace" font-size="46" font-weight="700"
|
||||
fill="#f85149" letter-spacing="-0.5">1,186</text>
|
||||
|
||||
|
Before Width: | Height: | Size: 2.7 KiB After Width: | Height: | Size: 2.7 KiB |
+2
-2
@@ -1,5 +1,5 @@
|
||||
{
|
||||
"kev": 1186,
|
||||
"total_cves": 171489,
|
||||
"with_pocs": 82728
|
||||
"total_cves": 171529,
|
||||
"with_pocs": 82768
|
||||
}
|
||||
@@ -1 +1 @@
|
||||
{"CVE-1999-0001":["2000-02-04","2024-08-01"],"CVE-1999-0002":["1999-09-29","2024-08-01"],"CVE-1999-0003":["1999-09-29","2024-08-01"],"CVE-1999-0004":["2000-02-04","2024-08-01"],"CVE-1999-0005":["1999-09-29","2024-08-01"],"CVE-1999-0006":["1999-09-29","2024-10-29"],"CVE-1999-0007":["1999-09-29","2024-08-01"],"CVE-1999-0009":["1999-09-29","2024-08-01"],"CVE-1999-0014":["1999-09-29","2024-08-01"],"CVE-1999-0015":["2000-02-04","2024-08-01"],"CVE-1999-0016":["1999-09-29","2025-03-17"],"CVE-1999-0018":["1999-09-29","2024-08-01"],"CVE-1999-0019":["1999-09-29","2024-08-01"],"CVE-1999-0021":["1999-09-29","2024-08-01"],"CVE-1999-0023":["1999-09-29","2024-08-01"],"CVE-1999-0025":["1999-09-29","2024-08-01"],"CVE-1999-0026":["1999-09-29","2024-08-01"],"CVE-1999-0027":["1999-09-29","2024-08-01"],"CVE-1999-0028":["1999-09-29","2024-08-01"],"CVE-1999-0029":["1999-09-29","2024-10-29"],"CVE-1999-0030":["2000-02-04","2024-08-01"],"CVE-1999-0032":["1999-09-29","2024-08-01"],"CVE-1999-0034":["1999-09-29","2024-08-01"],"CVE-1999-0036":["1999-09-29","2024-10-29"],"CVE-1999-0038":["1999-09-29","2024-09-12"],"CVE-1999-0039":["1999-09-29","2024-09-12"],"CVE-1999-0040":["1999-09-29","2024-08-01"],"CVE-1999-0041":["1999-09-29","2024-09-17"],"CVE-1999-0042":["1999-09-29","2024-08-01"],"CVE-1999-0044":["1999-09-29","2024-08-01"],"CVE-1999-0045":["1999-09-29","2024-08-01"],"CVE-1999-0046":["1999-09-29","2024-08-01"],"CVE-1999-0050":["1999-09-29","2024-08-01"],"CVE-1999-0051":["1999-09-29","2024-08-01"],"CVE-1999-0060":["1999-09-29","2024-08-01"],"CVE-1999-0063":["1999-09-29","2024-08-01"],"CVE-1999-0064":["1999-09-29","2024-08-01"],"CVE-1999-0066":["1999-09-29","2024-08-01"],"CVE-1999-0067":["1999-09-29","2024-08-01"],"CVE-1999-0068":["1999-09-29","2024-08-01"],"CVE-1999-0069":["1999-09-29","2024-08-01"],"CVE-1999-0070":["1999-09-29","2024-08-01"],"CVE-1999-0077":["1999-09-29","2024-08-01"],"CVE-1999-0078":["2000-02-04","2024-08-01"],"CVE-1999-0082":["1999-09-29","2024-08-01"],"CVE-1999-0084":["1999-09-29","2024-08-01"],"CVE-1999-0088":["2000-02-04","2024-08-01"],"CVE-1999-0092":["2000-02-04","2024-08-01"],"CVE-1999-0095":["1999-09-29","2024-08-01"],"CVE-1999-0101":["2000-01-18","2024-08-01"],"CVE-1999-0103":["1999-09-29","2025-03-17"],"CVE-1999-0105":["2000-02-04","2024-08-01"],"CVE-1999-0107":["2000-02-04","2024-08-01"],"CVE-1999-0108":["1999-09-29","2024-08-01"],"CVE-1999-0109":["1999-09-29","2024-08-01"],"CVE-1999-0110":["2000-02-04","2005-02-04"],"CVE-1999-0112":["1999-09-29","2024-08-01"],"CVE-1999-0113":["1999-09-29","2024-08-01"],"CVE-1999-0115":["2001-05-07","2024-08-01"],"CVE-1999-0116":["1999-09-29","2024-08-01"],"CVE-1999-0118":["2000-06-02","2024-08-01"],"CVE-1999-0122":["1999-09-29","2024-08-01"],"CVE-1999-0125":["1999-09-29","2024-08-01"],"CVE-1999-0126":["1999-09-29","2024-08-01"],"CVE-1999-0128":["1999-09-29","2024-08-01"],"CVE-1999-0130":["1999-09-29","2024-08-01"],"CVE-1999-0137":["1999-09-29","2024-08-01"],"CVE-1999-0140":["2000-02-04","2024-08-01"],"CVE-1999-0144":["2000-02-04","2024-08-01"],"CVE-1999-0145":["2000-10-13","2024-08-01"],"CVE-1999-0146":["1999-09-29","2024-08-01"],"CVE-1999-0147":["1999-09-29","2024-08-01"],"CVE-1999-0148":["1999-09-29","2024-08-01"],"CVE-1999-0149":["1999-09-29","2024-08-01"],"CVE-1999-0153":["1999-09-29","2024-08-01"],"CVE-1999-0154":["2001-09-12","2024-08-01"],"CVE-1999-0156":["2000-02-04","2024-08-01"],"CVE-1999-0158":["1999-09-29","2024-08-01"],"CVE-1999-0162":["1999-09-29","2024-08-01"],"CVE-1999-0163":["2000-02-04","2024-08-01"],"CVE-1999-0165":["2000-02-04","2024-08-01"],"CVE-1999-0170":["1999-09-29","2024-08-01"],"CVE-1999-0173":["1999-09-29","2024-08-01"],"CVE-1999-0174":["1999-09-29","2024-08-01"],"CVE-1999-0175":["1999-09-29","2024-08-01"],"CVE-1999-0176":["1999-09-29","2024-08-01"],"CVE-1999-0178":["1999-09-29","2024-08-01"],"CVE-1999-0180":["1999-09-29","2024-08-01"],"CVE-1999-0182":["1999-09-29","2024-08-01"],"CVE-1999-0183":["1999-09-29","2024-08-01"],"CVE-1999-0191":["1999-09-29","2024-08-01"],"CVE-1999-0192":["1999-09-29","2024-08-01"],"CVE-1999-0193":["2000-02-04","2024-08-01"],"CVE-1999-0195":["2000-02-04","2024-08-01"],"CVE-1999-0196":["1999-09-29","2024-08-01"],"CVE-1999-0199":["2020-10-06","2024-08-01"],"CVE-1999-0201":["1999-09-29","2024-08-01"],"CVE-1999-0204":["1999-09-29","2024-08-01"],"CVE-1999-0206":["1999-09-29","2024-08-01"],"CVE-1999-0207":["1999-09-29","2024-08-01"],"CVE-1999-0208":["1999-09-29","2024-08-01"],"CVE-1999-0209":["1999-09-29","2024-08-01"],"CVE-1999-0210":["2000-06-02","2024-08-01"],"CVE-1999-0211":["1999-09-29","2024-08-01"],"CVE-1999-0215":["1999-09-29","2024-08-01"],"CVE-1999-0219":["1999-09-29","2024-08-01"],"CVE-1999-0220":["2000-02-04","2024-08-01"],"CVE-1999-0221":["1999-09-29","2024-08-01"],"CVE-1999-0224":["1999-09-29","2024-08-01"],"CVE-1999-0225":["2000-06-02","2024-08-01"],"CVE-1999-0232":["2000-02-04","2024-08-01"],"CVE-1999-0233":["2000-01-18","2024-08-01"],"CVE-1999-0235":["2000-02-04","2024-08-01"],"CVE-1999-0236":["1999-09-Line truncated
|
||||
{"CVE-1999-0001":["2000-02-04","2024-08-01"],"CVE-1999-0002":["1999-09-29","2024-08-01"],"CVE-1999-0003":["1999-09-29","2024-08-01"],"CVE-1999-0004":["2000-02-04","2024-08-01"],"CVE-1999-0005":["1999-09-29","2024-08-01"],"CVE-1999-0006":["1999-09-29","2024-10-29"],"CVE-1999-0007":["1999-09-29","2024-08-01"],"CVE-1999-0009":["1999-09-29","2024-08-01"],"CVE-1999-0014":["1999-09-29","2024-08-01"],"CVE-1999-0015":["2000-02-04","2024-08-01"],"CVE-1999-0016":["1999-09-29","2025-03-17"],"CVE-1999-0018":["1999-09-29","2024-08-01"],"CVE-1999-0019":["1999-09-29","2024-08-01"],"CVE-1999-0021":["1999-09-29","2024-08-01"],"CVE-1999-0023":["1999-09-29","2024-08-01"],"CVE-1999-0025":["1999-09-29","2024-08-01"],"CVE-1999-0026":["1999-09-29","2024-08-01"],"CVE-1999-0027":["1999-09-29","2024-08-01"],"CVE-1999-0028":["1999-09-29","2024-08-01"],"CVE-1999-0029":["1999-09-29","2024-10-29"],"CVE-1999-0030":["2000-02-04","2024-08-01"],"CVE-1999-0032":["1999-09-29","2024-08-01"],"CVE-1999-0034":["1999-09-29","2024-08-01"],"CVE-1999-0036":["1999-09-29","2024-10-29"],"CVE-1999-0038":["1999-09-29","2024-09-12"],"CVE-1999-0039":["1999-09-29","2024-09-12"],"CVE-1999-0040":["1999-09-29","2024-08-01"],"CVE-1999-0041":["1999-09-29","2024-09-17"],"CVE-1999-0042":["1999-09-29","2024-08-01"],"CVE-1999-0044":["1999-09-29","2024-08-01"],"CVE-1999-0045":["1999-09-29","2024-08-01"],"CVE-1999-0046":["1999-09-29","2024-08-01"],"CVE-1999-0050":["1999-09-29","2024-08-01"],"CVE-1999-0051":["1999-09-29","2024-08-01"],"CVE-1999-0060":["1999-09-29","2024-08-01"],"CVE-1999-0063":["1999-09-29","2024-08-01"],"CVE-1999-0064":["1999-09-29","2024-08-01"],"CVE-1999-0066":["1999-09-29","2024-08-01"],"CVE-1999-0067":["1999-09-29","2024-08-01"],"CVE-1999-0068":["1999-09-29","2024-08-01"],"CVE-1999-0069":["1999-09-29","2024-08-01"],"CVE-1999-0070":["1999-09-29","2024-08-01"],"CVE-1999-0077":["1999-09-29","2024-08-01"],"CVE-1999-0078":["2000-02-04","2024-08-01"],"CVE-1999-0082":["1999-09-29","2024-08-01"],"CVE-1999-0084":["1999-09-29","2024-08-01"],"CVE-1999-0088":["2000-02-04","2024-08-01"],"CVE-1999-0092":["2000-02-04","2024-08-01"],"CVE-1999-0095":["1999-09-29","2024-08-01"],"CVE-1999-0101":["2000-01-18","2024-08-01"],"CVE-1999-0103":["1999-09-29","2025-03-17"],"CVE-1999-0105":["2000-02-04","2024-08-01"],"CVE-1999-0107":["2000-02-04","2024-08-01"],"CVE-1999-0108":["1999-09-29","2024-08-01"],"CVE-1999-0109":["1999-09-29","2024-08-01"],"CVE-1999-0110":["2000-02-04","2005-02-04"],"CVE-1999-0112":["1999-09-29","2024-08-01"],"CVE-1999-0113":["1999-09-29","2024-08-01"],"CVE-1999-0115":["2001-05-07","2024-08-01"],"CVE-1999-0116":["1999-09-29","2024-08-01"],"CVE-1999-0118":["2000-06-02","2024-08-01"],"CVE-1999-0122":["1999-09-29","2024-08-01"],"CVE-1999-0125":["1999-09-29","2024-08-01"],"CVE-1999-0126":["1999-09-29","2024-08-01"],"CVE-1999-0128":["1999-09-29","2024-08-01"],"CVE-1999-0130":["1999-09-29","2024-08-01"],"CVE-1999-0137":["1999-09-29","2024-08-01"],"CVE-1999-0140":["2000-02-04","2024-08-01"],"CVE-1999-0144":["2000-02-04","2024-08-01"],"CVE-1999-0145":["2000-10-13","2024-08-01"],"CVE-1999-0146":["1999-09-29","2024-08-01"],"CVE-1999-0147":["1999-09-29","2024-08-01"],"CVE-1999-0148":["1999-09-29","2024-08-01"],"CVE-1999-0149":["1999-09-29","2024-08-01"],"CVE-1999-0153":["1999-09-29","2024-08-01"],"CVE-1999-0154":["2001-09-12","2024-08-01"],"CVE-1999-0156":["2000-02-04","2024-08-01"],"CVE-1999-0158":["1999-09-29","2024-08-01"],"CVE-1999-0162":["1999-09-29","2024-08-01"],"CVE-1999-0163":["2000-02-04","2024-08-01"],"CVE-1999-0165":["2000-02-04","2024-08-01"],"CVE-1999-0170":["1999-09-29","2024-08-01"],"CVE-1999-0173":["1999-09-29","2024-08-01"],"CVE-1999-0174":["1999-09-29","2024-08-01"],"CVE-1999-0175":["1999-09-29","2024-08-01"],"CVE-1999-0176":["1999-09-29","2024-08-01"],"CVE-1999-0178":["1999-09-29","2024-08-01"],"CVE-1999-0180":["1999-09-29","2024-08-01"],"CVE-1999-0182":["1999-09-29","2024-08-01"],"CVE-1999-0183":["1999-09-29","2024-08-01"],"CVE-1999-0191":["1999-09-29","2024-08-01"],"CVE-1999-0192":["1999-09-29","2024-08-01"],"CVE-1999-0193":["2000-02-04","2024-08-01"],"CVE-1999-0195":["2000-02-04","2024-08-01"],"CVE-1999-0196":["1999-09-29","2024-08-01"],"CVE-1999-0199":["2020-10-06","2024-08-01"],"CVE-1999-0201":["1999-09-29","2024-08-01"],"CVE-1999-0204":["1999-09-29","2024-08-01"],"CVE-1999-0206":["1999-09-29","2024-08-01"],"CVE-1999-0207":["1999-09-29","2024-08-01"],"CVE-1999-0208":["1999-09-29","2024-08-01"],"CVE-1999-0209":["1999-09-29","2024-08-01"],"CVE-1999-0210":["2000-06-02","2024-08-01"],"CVE-1999-0211":["1999-09-29","2024-08-01"],"CVE-1999-0215":["1999-09-29","2024-08-01"],"CVE-1999-0219":["1999-09-29","2024-08-01"],"CVE-1999-0220":["2000-02-04","2024-08-01"],"CVE-1999-0221":["1999-09-29","2024-08-01"],"CVE-1999-0224":["1999-09-29","2024-08-01"],"CVE-1999-0225":["2000-06-02","2024-08-01"],"CVE-1999-0232":["2000-02-04","2024-08-01"],"CVE-1999-0233":["2000-01-18","2024-08-01"],"CVE-1999-0235":["2000-02-04","2024-08-01"],"CVE-1999-0236":["1999-09-Line truncated
|
||||
@@ -1 +1 @@
|
||||
{"CVE-1999-0110":{"checked":"2026-09-01","status":"REJECTED"},"CVE-1999-0335":{"checked":"2026-09-01","status":"REJECTED"},"CVE-1999-0531":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2002-0192":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2002-0828":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2003-0090":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2005-0122":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2005-0153":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2005-1032":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2005-2116":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2005-2303":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2005-4633":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2006-3866":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2006-4216":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2007-1570":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2007-5125":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2008-2737":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2008-4042":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2008-4112":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2008-4189":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2008-4270":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2008-6049":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2008-6628":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2009-0300":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2009-0795":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2009-2259":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2010-0368":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2010-2782":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2010-2972":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2010-3885":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2011-0108":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2011-1656":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2011-2553":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2011-3633":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2011-4779":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2011-5232":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2012-0722":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2012-1300":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2012-1304":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2012-1305":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2012-1309":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2012-1913":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2012-2216":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2012-2344":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2012-2765":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2012-3539":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2012-4748":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2012-4749":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2012-6315":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2012-6679":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2013-1298":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-1625":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2013-1805":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-2649":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2013-2749":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-3130":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-4266":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5575":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5581":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5621":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5622":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5623":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5624":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5625":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5627":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5628":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5630":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5631":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5632":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5633":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5689":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5759":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2014-0982":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2014-1004":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2014-1137":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2014-1155":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2014-1470":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2014-2085":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2014-2239":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2014-2923":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2014-2937":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2Line truncated
|
||||
{"CVE-1999-0110":{"checked":"2026-09-01","status":"REJECTED"},"CVE-1999-0335":{"checked":"2026-09-01","status":"REJECTED"},"CVE-1999-0531":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2002-0192":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2002-0828":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2003-0090":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2005-0122":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2005-0153":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2005-1032":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2005-2116":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2005-2303":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2005-4633":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2006-3866":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2006-4216":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2007-1570":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2007-5125":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2008-2737":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2008-4042":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2008-4112":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2008-4189":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2008-4270":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2008-6049":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2008-6628":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2009-0300":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2009-0795":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2009-2259":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2010-0368":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2010-2782":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2010-2972":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2010-3885":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2011-0108":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2011-1656":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2011-2553":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2011-3633":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2011-4779":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2011-5232":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2012-0722":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2012-1300":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2012-1304":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2012-1305":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2012-1309":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2012-1913":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2012-2216":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2012-2344":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2012-2765":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2012-3539":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2012-4748":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2012-4749":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2012-6315":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2012-6679":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2013-1298":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-1625":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2013-1805":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-2649":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2013-2749":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-3130":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-4266":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5575":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5581":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5621":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5622":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5623":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5624":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5625":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5627":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5628":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5630":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5631":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5632":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5633":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5689":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-5759":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2014-0982":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2014-1004":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2014-1137":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2014-1155":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2014-1470":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2014-2085":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2014-2239":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2014-2923":{"checked":"2026-09-08","status":"UNAVAILABLE"},"CVE-2014-2937":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2Line truncated
|
||||
@@ -1 +1 @@
|
||||
{"GHSA-222V-CX2C-Q2F5":["CVE-2025-24530","https://github.com/advisories/GHSA-222v-cx2c-q2f5",[["3.1",6.4,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2025-11-03T22:54:20Z"],"GHSA-222W-XMC5-JHP3":["CVE-2025-43735","https://github.com/advisories/GHSA-222w-xmc5-jhp3",[["4.0",6.9,"MEDIUM","CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2025-08-12T21:04:35Z"],"GHSA-2234-FMW7-43WR":["CVE-2024-48913","https://github.com/advisories/GHSA-2234-fmw7-43wr",[["3.1",5.9,"MEDIUM","CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:N","GitHub Advisory Database","GitHub Reviewed"]],1,"2024-11-07T18:33:22Z"],"GHSA-2238-XC5R-V9HJ":["CVE-2026-24125","https://github.com/advisories/GHSA-2238-xc5r-v9hj",[["3.1",6.3,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","GitHub Advisory Database","GitHub Reviewed"]],1,"2026-03-12T19:13:57Z"],"GHSA-223G-8W3X-98WR":["CVE-2023-34230","https://github.com/advisories/GHSA-223g-8w3x-98wr",[["3.1",7.3,"HIGH","CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2023-11-06T05:04:15Z"],"GHSA-223G-F5MQ-GW33":["CVE-2026-44720","https://github.com/advisories/GHSA-223g-f5mq-gw33",[["4.0",6.9,"MEDIUM","CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2026-06-08T23:54:58Z"],"GHSA-223J-4RM8-MRMF":["CVE-2025-30218","https://github.com/advisories/GHSA-223j-4rm8-mrmf",[["4.0",1.7,"LOW","CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U","GitHub Advisory Database","GitHub Reviewed"]],0,"2025-10-13T15:35:51Z"],"GHSA-223M-4RFP-646H":["CVE-2025-59475","https://github.com/advisories/GHSA-223m-4rfp-646h",[["3.1",4.3,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2025-11-05T20:45:04Z"],"GHSA-223M-PGCQ-F3XG":["CVE-2023-4303","https://github.com/advisories/GHSA-223m-pgcq-f3xg",[["3.1",4.3,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2023-11-09T05:03:23Z"],"GHSA-2259-H742-5VR4":["CVE-2021-20250","https://github.com/advisories/GHSA-2259-h742-5vr4",[["3.1",4.3,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2023-01-31T05:01:19Z"],"GHSA-225X-3JHX-WH4Q":["CVE-2026-64664","https://github.com/advisories/GHSA-225x-3jhx-wh4q",[["3.1",4.3,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2026-08-06T19:22:35Z"],"GHSA-2263-JWGM-WV97":["CVE-2018-16342","https://github.com/advisories/GHSA-2263-jwgm-wv97",[["3.0",5.4,"MEDIUM","CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2023-10-06T18:02:31Z"],"GHSA-2267-XQCF-GW2M":["CVE-2025-69210","https://github.com/advisories/GHSA-2267-xqcf-gw2m",[["4.0",8.6,"HIGH","CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2026-01-02T22:51:53Z"],"GHSA-2268-98WH-QFHF":["CVE-2023-50572","https://github.com/advisories/GHSA-2268-98wh-qfhf",[["3.1",5.5,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","GitHub Advisory Database","GitHub Reviewed"]],0,"2024-01-05T19:49:51Z"],"GHSA-226F-F24G-524W":["CVE-2026-54008","https://github.com/advisories/GHSA-226f-f24g-524w",[["3.1",8.5,"HIGH","CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N","GitHub Advisory Database","GitHub Reviewed"]],1,"2026-06-17T14:10:58Z"],"GHSA-226H-QRG4-8236":["CVE-2020-2269","https://github.com/advisories/GHSA-226h-qrg4-8236",[["3.1",8.0,"HIGH","CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","GitHub Advisory Database","GitHub Reviewed"]],0,"2023-01-28T05:06:32Z"],"GHSA-2275-RPF5-XV8H":["CVE-2022-25906","https://github.com/advisories/GHSA-2275-rpf5-xv8h",[["3.1",7.8,"HIGH","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","GitHub Advisory Database","GitHub Reviewed"]],0,"2025-03-27T03:50:00Z"],"GHSA-227G-7CVV-6FF3":["CVE-2022-31781","https://github.com/advisories/GHSA-227g-7cvv-6ff3",[["3.1",7.5,"HIGH","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","GitHub Advisory Database","GitHub Reviewed"]],0,"2023-07-24T19:38:55Z"],"GHSA-227R-JM2G-7CP4":["CVE-2026-50201","https://github.com/advisories/GHSA-227r-jm2g-7cp4",[["3.1",6.5,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2026-07-02T20:31:28Z"],"GHSA-227R-W5J2-6243":["CVE-2024-11042","https://github.com/advisories/GHSA-227r-w5j2-6243",[["3.0",9.1,"CRITICAL","CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H","GitHub Advisory Database","GitHub Reviewed"]],0,"2025-10-15T16:03:29Z"],"GHSA-227W-WV4J-67H4":["CVE-2024-23682","https://github.com/advisories/GHSA-227w-wv4j-67h4",[["3.1",8.2,"HIGH","CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H","GitHub Advisory Database","GitHub Reviewed"]],0,"2026-01-22T20:53:44Z"],"GHSA-227X-7MH8-3CF6":["CVE-2025-59823","hLine truncated
|
||||
{"GHSA-222V-CX2C-Q2F5":["CVE-2025-24530","https://github.com/advisories/GHSA-222v-cx2c-q2f5",[["3.1",6.4,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2025-11-03T22:54:20Z"],"GHSA-222W-XMC5-JHP3":["CVE-2025-43735","https://github.com/advisories/GHSA-222w-xmc5-jhp3",[["4.0",6.9,"MEDIUM","CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2025-08-12T21:04:35Z"],"GHSA-2234-FMW7-43WR":["CVE-2024-48913","https://github.com/advisories/GHSA-2234-fmw7-43wr",[["3.1",5.9,"MEDIUM","CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:N","GitHub Advisory Database","GitHub Reviewed"]],1,"2024-11-07T18:33:22Z"],"GHSA-2238-XC5R-V9HJ":["CVE-2026-24125","https://github.com/advisories/GHSA-2238-xc5r-v9hj",[["3.1",6.3,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","GitHub Advisory Database","GitHub Reviewed"]],1,"2026-03-12T19:13:57Z"],"GHSA-223G-8W3X-98WR":["CVE-2023-34230","https://github.com/advisories/GHSA-223g-8w3x-98wr",[["3.1",7.3,"HIGH","CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2023-11-06T05:04:15Z"],"GHSA-223G-F5MQ-GW33":["CVE-2026-44720","https://github.com/advisories/GHSA-223g-f5mq-gw33",[["4.0",6.9,"MEDIUM","CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2026-06-08T23:54:58Z"],"GHSA-223J-4RM8-MRMF":["CVE-2025-30218","https://github.com/advisories/GHSA-223j-4rm8-mrmf",[["4.0",1.7,"LOW","CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U","GitHub Advisory Database","GitHub Reviewed"]],0,"2025-10-13T15:35:51Z"],"GHSA-223M-4RFP-646H":["CVE-2025-59475","https://github.com/advisories/GHSA-223m-4rfp-646h",[["3.1",4.3,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2025-11-05T20:45:04Z"],"GHSA-223M-PGCQ-F3XG":["CVE-2023-4303","https://github.com/advisories/GHSA-223m-pgcq-f3xg",[["3.1",4.3,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2023-11-09T05:03:23Z"],"GHSA-2259-H742-5VR4":["CVE-2021-20250","https://github.com/advisories/GHSA-2259-h742-5vr4",[["3.1",4.3,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2023-01-31T05:01:19Z"],"GHSA-225X-3JHX-WH4Q":["CVE-2026-64664","https://github.com/advisories/GHSA-225x-3jhx-wh4q",[["3.1",4.3,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2026-08-06T19:22:35Z"],"GHSA-2263-JWGM-WV97":["CVE-2018-16342","https://github.com/advisories/GHSA-2263-jwgm-wv97",[["3.0",5.4,"MEDIUM","CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2023-10-06T18:02:31Z"],"GHSA-2267-XQCF-GW2M":["CVE-2025-69210","https://github.com/advisories/GHSA-2267-xqcf-gw2m",[["4.0",8.6,"HIGH","CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2026-01-02T22:51:53Z"],"GHSA-2268-98WH-QFHF":["CVE-2023-50572","https://github.com/advisories/GHSA-2268-98wh-qfhf",[["3.1",5.5,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","GitHub Advisory Database","GitHub Reviewed"]],0,"2024-01-05T19:49:51Z"],"GHSA-226F-F24G-524W":["CVE-2026-54008","https://github.com/advisories/GHSA-226f-f24g-524w",[["3.1",8.5,"HIGH","CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N","GitHub Advisory Database","GitHub Reviewed"]],1,"2026-06-17T14:10:58Z"],"GHSA-226H-QRG4-8236":["CVE-2020-2269","https://github.com/advisories/GHSA-226h-qrg4-8236",[["3.1",8.0,"HIGH","CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","GitHub Advisory Database","GitHub Reviewed"]],0,"2023-01-28T05:06:32Z"],"GHSA-2275-RPF5-XV8H":["CVE-2022-25906","https://github.com/advisories/GHSA-2275-rpf5-xv8h",[["3.1",7.8,"HIGH","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","GitHub Advisory Database","GitHub Reviewed"]],0,"2025-03-27T03:50:00Z"],"GHSA-227G-7CVV-6FF3":["CVE-2022-31781","https://github.com/advisories/GHSA-227g-7cvv-6ff3",[["3.1",7.5,"HIGH","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","GitHub Advisory Database","GitHub Reviewed"]],0,"2023-07-24T19:38:55Z"],"GHSA-227R-JM2G-7CP4":["CVE-2026-50201","https://github.com/advisories/GHSA-227r-jm2g-7cp4",[["3.1",6.5,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","GitHub Advisory Database","GitHub Reviewed"]],0,"2026-07-02T20:31:28Z"],"GHSA-227R-W5J2-6243":["CVE-2024-11042","https://github.com/advisories/GHSA-227r-w5j2-6243",[["3.0",9.1,"CRITICAL","CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H","GitHub Advisory Database","GitHub Reviewed"]],0,"2025-10-15T16:03:29Z"],"GHSA-227W-WV4J-67H4":["CVE-2024-23682","https://github.com/advisories/GHSA-227w-wv4j-67h4",[["3.1",8.2,"HIGH","CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H","GitHub Advisory Database","GitHub Reviewed"]],0,"2026-01-22T20:53:44Z"],"GHSA-227X-7MH8-3CF6":["CVE-2025-59823","hLine truncated
|
||||
+1
-1
@@ -1 +1 @@
|
||||
{"CVE-2002-0367":["2022-03-03",0],"CVE-2004-0210":["2022-03-03",0],"CVE-2004-1464":["2023-05-19",0],"CVE-2005-2773":["2022-03-25",0],"CVE-2006-1547":["2022-01-21",0],"CVE-2006-2492":["2022-06-08",0],"CVE-2007-0671":["2025-08-12",0],"CVE-2007-3010":["2022-04-15",0],"CVE-2007-5659":["2022-06-08",0],"CVE-2008-0015":["2026-02-17",0],"CVE-2008-0655":["2022-06-08",0],"CVE-2008-2992":["2022-03-03",1],"CVE-2008-3431":["2022-03-03",0],"CVE-2008-4128":["2026-07-13",0],"CVE-2008-4250":["2026-05-20",0],"CVE-2009-0238":["2026-04-14",0],"CVE-2009-0556":["2026-01-07",0],"CVE-2009-0557":["2022-06-08",0],"CVE-2009-0563":["2022-06-08",0],"CVE-2009-0927":["2022-03-25",0],"CVE-2009-1123":["2022-03-03",0],"CVE-2009-1151":["2022-03-25",0],"CVE-2009-1537":["2026-05-20",0],"CVE-2009-1862":["2022-06-08",0],"CVE-2009-2055":["2022-03-25",0],"CVE-2009-3129":["2022-03-03",0],"CVE-2009-3459":["2026-05-20",0],"CVE-2009-3953":["2022-06-08",0],"CVE-2009-3960":["2022-03-07",1],"CVE-2009-4324":["2022-06-08",0],"CVE-2010-0188":["2022-03-03",1],"CVE-2010-0232":["2022-03-03",0],"CVE-2010-0249":["2026-05-20",0],"CVE-2010-0738":["2022-05-25",1],"CVE-2010-0806":["2026-05-20",0],"CVE-2010-0840":["2022-05-25",0],"CVE-2010-1297":["2022-06-08",0],"CVE-2010-1428":["2022-05-25",1],"CVE-2010-1871":["2021-12-10",0],"CVE-2010-2568":["2022-09-15",0],"CVE-2010-2572":["2022-06-08",0],"CVE-2010-2861":["2022-03-25",1],"CVE-2010-2883":["2022-06-08",0],"CVE-2010-3035":["2022-03-25",0],"CVE-2010-3333":["2022-03-03",0],"CVE-2010-3765":["2025-10-06",0],"CVE-2010-3904":["2023-05-12",0],"CVE-2010-3962":["2025-10-06",0],"CVE-2010-4344":["2022-03-25",0],"CVE-2010-4345":["2022-03-25",0],"CVE-2010-4398":["2022-03-28",0],"CVE-2010-5326":["2021-11-03",0],"CVE-2010-5330":["2022-04-15",0],"CVE-2011-0609":["2022-06-08",0],"CVE-2011-0611":["2022-03-03",0],"CVE-2011-1823":["2022-09-08",0],"CVE-2011-1889":["2022-03-03",0],"CVE-2011-2005":["2022-03-28",0],"CVE-2011-2462":["2022-06-08",0],"CVE-2011-3402":["2025-10-06",0],"CVE-2011-3544":["2022-03-03",0],"CVE-2011-4723":["2022-09-08",0],"CVE-2012-0151":["2022-06-08",0],"CVE-2012-0158":["2021-11-03",1],"CVE-2012-0391":["2022-01-21",0],"CVE-2012-0507":["2022-03-03",1],"CVE-2012-0518":["2022-03-28",0],"CVE-2012-0754":["2022-06-08",0],"CVE-2012-0767":["2022-06-08",0],"CVE-2012-1535":["2022-03-03",0],"CVE-2012-1710":["2022-05-25",1],"CVE-2012-1723":["2022-03-03",1],"CVE-2012-1823":["2022-03-25",0],"CVE-2012-1854":["2026-04-13",0],"CVE-2012-1856":["2022-03-03",0],"CVE-2012-1889":["2022-06-08",0],"CVE-2012-2034":["2022-03-28",0],"CVE-2012-2539":["2022-03-28",0],"CVE-2012-3152":["2021-11-03",0],"CVE-2012-4681":["2022-03-03",1],"CVE-2012-4792":["2024-07-23",0],"CVE-2012-4969":["2022-06-08",0],"CVE-2012-5054":["2022-06-08",0],"CVE-2012-5076":["2022-03-28",0],"CVE-2013-0074":["2022-05-25",1],"CVE-2013-0422":["2022-05-25",1],"CVE-2013-0431":["2022-05-25",1],"CVE-2013-0625":["2022-03-07",0],"CVE-2013-0629":["2022-03-07",0],"CVE-2013-0631":["2022-03-07",0],"CVE-2013-0632":["2022-03-03",0],"CVE-2013-0640":["2022-03-03",0],"CVE-2013-0641":["2022-03-03",0],"CVE-2013-0643":["2024-09-17",0],"CVE-2013-0648":["2024-09-17",0],"CVE-2013-1331":["2022-06-08",0],"CVE-2013-1347":["2022-03-03",0],"CVE-2013-1675":["2022-03-03",0],"CVE-2013-1690":["2022-03-28",0],"CVE-2013-2094":["2022-09-15",0],"CVE-2013-2251":["2022-03-25",0],"CVE-2013-2423":["2022-05-25",0],"CVE-2013-2465":["2022-03-28",1],"CVE-2013-2551":["2022-03-28",1],"CVE-2013-2596":["2022-09-15",0],"CVE-2013-2597":["2022-09-15",0],"CVE-2013-2729":["2022-03-28",0],"CVE-2013-3163":["2023-03-30",0],"CVE-2013-3346":["2022-03-03",0],"CVE-2013-3660":["2022-03-28",0],"CVE-2013-3893":["2025-08-12",0],"CVE-2013-3896":["2022-05-25",0],"CVE-2013-3897":["2022-03-03",0],"CVE-2013-3900":["2022-01-10",0],"CVE-2013-3906":["2022-02-15",0],"CVE-2013-3918":["2025-10-06",0],"CVE-2013-3993":["2022-05-25",1],"CVE-2013-4810":["2022-03-25",0],"CVE-2013-5065":["2022-03-03",0],"CVE-2013-5223":["2022-03-25",0],"CVE-2013-6282":["2022-09-15",0],"CVE-2013-7331":["2022-05-25",0],"CVE-2014-0130":["2022-03-25",0],"CVE-2014-0160":["2022-05-04",0],"CVE-2014-0196":["2023-05-12",0],"CVE-2014-0322":["2022-05-04",0],"CVE-2014-0496":["2022-03-03",0],"CVE-2014-0497":["2024-09-17",0],"CVE-2014-0502":["2024-09-17",0],"CVE-2014-0546":["2022-05-25",0],"CVE-2014-0780":["2022-04-15",0],"CVE-2014-100005":["2024-05-16",0],"CVE-2014-1761":["2022-02-15",0],"CVE-2014-1776":["2022-01-28",0],"CVE-2014-1812":["2021-11-03",1],"CVE-2014-2120":["2024-11-12",0],"CVE-2014-2817":["2022-05-25",0],"CVE-2014-3120":["2022-03-25",0],"CVE-2014-3153":["2022-05-25",0],"CVE-2014-3931":["2025-07-07",0],"CVE-2014-4077":["2022-05-25",0],"CVE-2014-4113":["2022-05-04",0],"CVE-2014-4114":["2022-03-03",0],"CVE-2014-4123":["2022-05-25",0],"CVE-2014-4148":["2022-05-25",0],"CVE-2014-4404":["2022-02-10",0],"CVE-2014-6271":["2022-01-28",0],"CVE-2014-6278":["2025-10-02",0],"CVE-2014-6287":["2022-03-25",0],"CVE-2014-6324":["2022-03-25",0],"CVE-2014-6332":["2022-03-25",0],"CVE-2014-635Line truncated
|
||||
{"CVE-2002-0367":["2022-03-03",0],"CVE-2004-0210":["2022-03-03",0],"CVE-2004-1464":["2023-05-19",0],"CVE-2005-2773":["2022-03-25",0],"CVE-2006-1547":["2022-01-21",0],"CVE-2006-2492":["2022-06-08",0],"CVE-2007-0671":["2025-08-12",0],"CVE-2007-3010":["2022-04-15",0],"CVE-2007-5659":["2022-06-08",0],"CVE-2008-0015":["2026-02-17",0],"CVE-2008-0655":["2022-06-08",0],"CVE-2008-2992":["2022-03-03",1],"CVE-2008-3431":["2022-03-03",0],"CVE-2008-4128":["2026-07-13",0],"CVE-2008-4250":["2026-05-20",0],"CVE-2009-0238":["2026-04-14",0],"CVE-2009-0556":["2026-01-07",0],"CVE-2009-0557":["2022-06-08",0],"CVE-2009-0563":["2022-06-08",0],"CVE-2009-0927":["2022-03-25",0],"CVE-2009-1123":["2022-03-03",0],"CVE-2009-1151":["2022-03-25",0],"CVE-2009-1537":["2026-05-20",0],"CVE-2009-1862":["2022-06-08",0],"CVE-2009-2055":["2022-03-25",0],"CVE-2009-3129":["2022-03-03",0],"CVE-2009-3459":["2026-05-20",0],"CVE-2009-3953":["2022-06-08",0],"CVE-2009-3960":["2022-03-07",1],"CVE-2009-4324":["2022-06-08",0],"CVE-2010-0188":["2022-03-03",1],"CVE-2010-0232":["2022-03-03",0],"CVE-2010-0249":["2026-05-20",0],"CVE-2010-0738":["2022-05-25",1],"CVE-2010-0806":["2026-05-20",0],"CVE-2010-0840":["2022-05-25",0],"CVE-2010-1297":["2022-06-08",0],"CVE-2010-1428":["2022-05-25",1],"CVE-2010-1871":["2021-12-10",0],"CVE-2010-2568":["2022-09-15",0],"CVE-2010-2572":["2022-06-08",0],"CVE-2010-2861":["2022-03-25",1],"CVE-2010-2883":["2022-06-08",0],"CVE-2010-3035":["2022-03-25",0],"CVE-2010-3333":["2022-03-03",0],"CVE-2010-3765":["2025-10-06",0],"CVE-2010-3904":["2023-05-12",0],"CVE-2010-3962":["2025-10-06",0],"CVE-2010-4344":["2022-03-25",0],"CVE-2010-4345":["2022-03-25",0],"CVE-2010-4398":["2022-03-28",0],"CVE-2010-5326":["2021-11-03",0],"CVE-2010-5330":["2022-04-15",0],"CVE-2011-0609":["2022-06-08",0],"CVE-2011-0611":["2022-03-03",0],"CVE-2011-1823":["2022-09-08",0],"CVE-2011-1889":["2022-03-03",0],"CVE-2011-2005":["2022-03-28",0],"CVE-2011-2462":["2022-06-08",0],"CVE-2011-3402":["2025-10-06",0],"CVE-2011-3544":["2022-03-03",0],"CVE-2011-4723":["2022-09-08",0],"CVE-2012-0151":["2022-06-08",0],"CVE-2012-0158":["2021-11-03",1],"CVE-2012-0391":["2022-01-21",0],"CVE-2012-0507":["2022-03-03",1],"CVE-2012-0518":["2022-03-28",0],"CVE-2012-0754":["2022-06-08",0],"CVE-2012-0767":["2022-06-08",0],"CVE-2012-1535":["2022-03-03",0],"CVE-2012-1710":["2022-05-25",1],"CVE-2012-1723":["2022-03-03",1],"CVE-2012-1823":["2022-03-25",0],"CVE-2012-1854":["2026-04-13",0],"CVE-2012-1856":["2022-03-03",0],"CVE-2012-1889":["2022-06-08",0],"CVE-2012-2034":["2022-03-28",0],"CVE-2012-2539":["2022-03-28",0],"CVE-2012-3152":["2021-11-03",0],"CVE-2012-4681":["2022-03-03",1],"CVE-2012-4792":["2024-07-23",0],"CVE-2012-4969":["2022-06-08",0],"CVE-2012-5054":["2022-06-08",0],"CVE-2012-5076":["2022-03-28",0],"CVE-2013-0074":["2022-05-25",1],"CVE-2013-0422":["2022-05-25",1],"CVE-2013-0431":["2022-05-25",1],"CVE-2013-0625":["2022-03-07",0],"CVE-2013-0629":["2022-03-07",0],"CVE-2013-0631":["2022-03-07",0],"CVE-2013-0632":["2022-03-03",0],"CVE-2013-0640":["2022-03-03",0],"CVE-2013-0641":["2022-03-03",0],"CVE-2013-0643":["2024-09-17",0],"CVE-2013-0648":["2024-09-17",0],"CVE-2013-1331":["2022-06-08",0],"CVE-2013-1347":["2022-03-03",0],"CVE-2013-1675":["2022-03-03",0],"CVE-2013-1690":["2022-03-28",0],"CVE-2013-2094":["2022-09-15",0],"CVE-2013-2251":["2022-03-25",0],"CVE-2013-2423":["2022-05-25",0],"CVE-2013-2465":["2022-03-28",1],"CVE-2013-2551":["2022-03-28",1],"CVE-2013-2596":["2022-09-15",0],"CVE-2013-2597":["2022-09-15",0],"CVE-2013-2729":["2022-03-28",0],"CVE-2013-3163":["2023-03-30",0],"CVE-2013-3346":["2022-03-03",0],"CVE-2013-3660":["2022-03-28",0],"CVE-2013-3893":["2025-08-12",0],"CVE-2013-3896":["2022-05-25",0],"CVE-2013-3897":["2022-03-03",0],"CVE-2013-3900":["2022-01-10",0],"CVE-2013-3906":["2022-02-15",0],"CVE-2013-3918":["2025-10-06",0],"CVE-2013-3993":["2022-05-25",1],"CVE-2013-4810":["2022-03-25",0],"CVE-2013-5065":["2022-03-03",0],"CVE-2013-5223":["2022-03-25",0],"CVE-2013-6282":["2022-09-15",0],"CVE-2013-7331":["2022-05-25",0],"CVE-2014-0130":["2022-03-25",0],"CVE-2014-0160":["2022-05-04",0],"CVE-2014-0196":["2023-05-12",0],"CVE-2014-0322":["2022-05-04",0],"CVE-2014-0496":["2022-03-03",0],"CVE-2014-0497":["2024-09-17",0],"CVE-2014-0502":["2024-09-17",0],"CVE-2014-0546":["2022-05-25",0],"CVE-2014-0780":["2022-04-15",0],"CVE-2014-100005":["2024-05-16",0],"CVE-2014-1761":["2022-02-15",0],"CVE-2014-1776":["2022-01-28",0],"CVE-2014-1812":["2021-11-03",1],"CVE-2014-2120":["2024-11-12",0],"CVE-2014-2817":["2022-05-25",0],"CVE-2014-3120":["2022-03-25",0],"CVE-2014-3153":["2022-05-25",0],"CVE-2014-3931":["2025-07-07",0],"CVE-2014-4077":["2022-05-25",0],"CVE-2014-4113":["2022-05-04",0],"CVE-2014-4114":["2022-03-03",0],"CVE-2014-4123":["2022-05-25",0],"CVE-2014-4148":["2022-05-25",0],"CVE-2014-4404":["2022-02-10",0],"CVE-2014-6271":["2022-01-28",0],"CVE-2014-6278":["2025-10-02",0],"CVE-2014-6287":["2022-03-25",0],"CVE-2014-6324":["2022-03-25",0],"CVE-2014-6332":["2022-03-25",0],"CVE-2014-635Line truncated
|
||||
@@ -1 +1 @@
|
||||
{"CVE-2020-0001":{"advisories":[["https://source.android.com/security/bulletin/2020-01-01",["Vendor Advisory"]]],"cvss":[["3.1",7.8,"HIGH","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"],["2.0",7.2,"HIGH","AV:L/AC:L/Au:N/C:C/I:C/A:C","[email protected]","Primary"]]},"CVE-2020-0002":{"advisories":[["https://source.android.com/security/bulletin/2020-01-01",["Vendor Advisory","Patch"]]],"cvss":[["3.1",8.8,"HIGH","CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","[email protected]","Primary"],["2.0",9.3,"HIGH","AV:N/AC:M/Au:N/C:C/I:C/A:C","[email protected]","Primary"]]},"CVE-2020-0003":{"advisories":[["https://source.android.com/security/bulletin/2020-01-01",["Vendor Advisory"]]],"cvss":[["3.1",6.7,"MEDIUM","CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H","[email protected]","Primary"],["2.0",3.7,"LOW","AV:L/AC:H/Au:N/C:P/I:P/A:P","[email protected]","Primary"]]},"CVE-2020-0004":{"advisories":[["https://source.android.com/security/bulletin/2020-01-01",["Vendor Advisory","Patch"]]],"cvss":[["3.1",5.5,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","[email protected]","Primary"],["2.0",4.9,"MEDIUM","AV:L/AC:L/Au:N/C:N/I:N/A:C","[email protected]","Primary"]]},"CVE-2020-0005":{"advisories":[["https://source.android.com/security/bulletin/2020-02-01",["Vendor Advisory","Patch"]]],"cvss":[["3.1",6.7,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"],["2.0",7.2,"HIGH","AV:L/AC:L/Au:N/C:C/I:C/A:C","[email protected]","Primary"]]},"CVE-2020-0006":{"advisories":[["https://source.android.com/security/bulletin/2020-01-01",["Vendor Advisory","Patch"]]],"cvss":[["3.1",6.5,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","[email protected]","Primary"],["2.0",4.3,"MEDIUM","AV:N/AC:M/Au:N/C:P/I:N/A:N","[email protected]","Primary"]]},"CVE-2020-0007":{"advisories":[["https://source.android.com/security/bulletin/2020-01-01",["Vendor Advisory"]]],"cvss":[["3.1",5.5,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","[email protected]","Primary"],["2.0",2.1,"LOW","AV:L/AC:L/Au:N/C:P/I:N/A:N","[email protected]","Primary"]]},"CVE-2020-0008":{"advisories":[["https://source.android.com/security/bulletin/2020-01-01",["Vendor Advisory","Patch"]]],"cvss":[["3.1",4.7,"MEDIUM","CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","[email protected]","Primary"],["2.0",1.9,"LOW","AV:L/AC:M/Au:N/C:P/I:N/A:N","[email protected]","Primary"]]},"CVE-2020-0009":{"advisories":[["https://source.android.com/security/bulletin/2020-01-01",["Vendor Advisory"]],["http://packetstormsecurity.com/files/155903/Android-ashmem-Read-Only-Bypasses.html",["Third Party Advisory","Patch"]],["https://lists.debian.org/debian-lts-announce/2020/06/msg00011.html",["Third Party Advisory"]],["https://lists.debian.org/debian-lts-announce/2020/06/msg00013.html",["Third Party Advisory"]]],"cvss":[["3.1",5.5,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","[email protected]","Primary"],["2.0",2.1,"LOW","AV:L/AC:L/Au:N/C:N/I:P/A:N","[email protected]","Primary"]]},"CVE-2020-0014":{"advisories":[["https://source.android.com/security/bulletin/2020-02-01",["Vendor Advisory"]]],"cvss":[["3.1",5.5,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","[email protected]","Primary"],["2.0",4.3,"MEDIUM","AV:N/AC:M/Au:N/C:P/I:N/A:N","[email protected]","Primary"]]},"CVE-2020-0015":{"advisories":[["https://source.android.com/security/bulletin/2020-02-01",["Vendor Advisory","Patch"]]],"cvss":[["3.1",7.8,"HIGH","CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","[email protected]","Primary"],["2.0",4.4,"MEDIUM","AV:L/AC:M/Au:N/C:P/I:P/A:P","[email protected]","Primary"]]},"CVE-2020-0016":{"advisories":[["https://source.android.com/security/bulletin/2020-12-01",["Vendor Advisory"]]],"cvss":[["3.1",7.8,"HIGH","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"],["2.0",7.2,"HIGH","AV:L/AC:L/Au:N/C:C/I:C/A:C","[email protected]","Primary"]]},"CVE-2020-0017":{"advisories":[["https://source.android.com/security/bulletin/2020-02-01",["Vendor Advisory","Patch"]]],"cvss":[["3.1",4.4,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N","[email protected]","Primary"],["2.0",3.3,"LOW","AV:L/AC:M/Au:N/C:P/I:P/A:N","[email protected]","Primary"]]},"CVE-2020-0018":{"advisories":[["https://source.android.com/security/bulletin/2020-02-01",["Vendor Advisory","Patch"]]],"cvss":[["3.1",4.4,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","[email protected]","Primary"],["2.0",2.1,"LOW","AV:L/AC:L/Au:N/C:P/I:N/A:N","[email protected]","Primary"]]},"CVE-2020-0019":{"advisories":[["https://source.android.com/security/bulletin/2020-12-01",["Vendor Advisory"]]],"cvss":[["3.1",5.5,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","[email protected]","Primary"],["2.0",2.1,"LOW","AV:L/AC:L/Au:N/C:P/I:N/A:N","[email protected]","Primary"]]},"CVE-2020-0022":{"advisories":[["https://source.android.com/security/bulletin/2020-02-01",["Vendor Advisory","Patch"]],["http://packetstormsecurity.com/files/156891/Android-Bluetooth-Remote-Denial-Of-Service.html",["Third Party Advisory","Exploit"]],["http://seclists.org/fulldisclosure/2020/Feb/10",["Third PLine truncated
|
||||
{"CVE-2020-0001":{"advisories":[["https://source.android.com/security/bulletin/2020-01-01",["Vendor Advisory"]]],"cvss":[["3.1",7.8,"HIGH","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"],["2.0",7.2,"HIGH","AV:L/AC:L/Au:N/C:C/I:C/A:C","[email protected]","Primary"]]},"CVE-2020-0002":{"advisories":[["https://source.android.com/security/bulletin/2020-01-01",["Vendor Advisory","Patch"]]],"cvss":[["3.1",8.8,"HIGH","CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","[email protected]","Primary"],["2.0",9.3,"HIGH","AV:N/AC:M/Au:N/C:C/I:C/A:C","[email protected]","Primary"]]},"CVE-2020-0003":{"advisories":[["https://source.android.com/security/bulletin/2020-01-01",["Vendor Advisory"]]],"cvss":[["3.1",6.7,"MEDIUM","CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H","[email protected]","Primary"],["2.0",3.7,"LOW","AV:L/AC:H/Au:N/C:P/I:P/A:P","[email protected]","Primary"]]},"CVE-2020-0004":{"advisories":[["https://source.android.com/security/bulletin/2020-01-01",["Vendor Advisory","Patch"]]],"cvss":[["3.1",5.5,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","[email protected]","Primary"],["2.0",4.9,"MEDIUM","AV:L/AC:L/Au:N/C:N/I:N/A:C","[email protected]","Primary"]]},"CVE-2020-0005":{"advisories":[["https://source.android.com/security/bulletin/2020-02-01",["Vendor Advisory","Patch"]]],"cvss":[["3.1",6.7,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"],["2.0",7.2,"HIGH","AV:L/AC:L/Au:N/C:C/I:C/A:C","[email protected]","Primary"]]},"CVE-2020-0006":{"advisories":[["https://source.android.com/security/bulletin/2020-01-01",["Vendor Advisory","Patch"]]],"cvss":[["3.1",6.5,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","[email protected]","Primary"],["2.0",4.3,"MEDIUM","AV:N/AC:M/Au:N/C:P/I:N/A:N","[email protected]","Primary"]]},"CVE-2020-0007":{"advisories":[["https://source.android.com/security/bulletin/2020-01-01",["Vendor Advisory"]]],"cvss":[["3.1",5.5,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","[email protected]","Primary"],["2.0",2.1,"LOW","AV:L/AC:L/Au:N/C:P/I:N/A:N","[email protected]","Primary"]]},"CVE-2020-0008":{"advisories":[["https://source.android.com/security/bulletin/2020-01-01",["Vendor Advisory","Patch"]]],"cvss":[["3.1",4.7,"MEDIUM","CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","[email protected]","Primary"],["2.0",1.9,"LOW","AV:L/AC:M/Au:N/C:P/I:N/A:N","[email protected]","Primary"]]},"CVE-2020-0009":{"advisories":[["https://source.android.com/security/bulletin/2020-01-01",["Vendor Advisory"]],["http://packetstormsecurity.com/files/155903/Android-ashmem-Read-Only-Bypasses.html",["Third Party Advisory","Patch"]],["https://lists.debian.org/debian-lts-announce/2020/06/msg00011.html",["Third Party Advisory"]],["https://lists.debian.org/debian-lts-announce/2020/06/msg00013.html",["Third Party Advisory"]]],"cvss":[["3.1",5.5,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","[email protected]","Primary"],["2.0",2.1,"LOW","AV:L/AC:L/Au:N/C:N/I:P/A:N","[email protected]","Primary"]]},"CVE-2020-0014":{"advisories":[["https://source.android.com/security/bulletin/2020-02-01",["Vendor Advisory"]]],"cvss":[["3.1",5.5,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","[email protected]","Primary"],["2.0",4.3,"MEDIUM","AV:N/AC:M/Au:N/C:P/I:N/A:N","[email protected]","Primary"]]},"CVE-2020-0015":{"advisories":[["https://source.android.com/security/bulletin/2020-02-01",["Vendor Advisory","Patch"]]],"cvss":[["3.1",7.8,"HIGH","CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","[email protected]","Primary"],["2.0",4.4,"MEDIUM","AV:L/AC:M/Au:N/C:P/I:P/A:P","[email protected]","Primary"]]},"CVE-2020-0016":{"advisories":[["https://source.android.com/security/bulletin/2020-12-01",["Vendor Advisory"]]],"cvss":[["3.1",7.8,"HIGH","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"],["2.0",7.2,"HIGH","AV:L/AC:L/Au:N/C:C/I:C/A:C","[email protected]","Primary"]]},"CVE-2020-0017":{"advisories":[["https://source.android.com/security/bulletin/2020-02-01",["Vendor Advisory","Patch"]]],"cvss":[["3.1",4.4,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N","[email protected]","Primary"],["2.0",3.3,"LOW","AV:L/AC:M/Au:N/C:P/I:P/A:N","[email protected]","Primary"]]},"CVE-2020-0018":{"advisories":[["https://source.android.com/security/bulletin/2020-02-01",["Vendor Advisory","Patch"]]],"cvss":[["3.1",4.4,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","[email protected]","Primary"],["2.0",2.1,"LOW","AV:L/AC:L/Au:N/C:P/I:N/A:N","[email protected]","Primary"]]},"CVE-2020-0019":{"advisories":[["https://source.android.com/security/bulletin/2020-12-01",["Vendor Advisory"]]],"cvss":[["3.1",5.5,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","[email protected]","Primary"],["2.0",2.1,"LOW","AV:L/AC:L/Au:N/C:P/I:N/A:N","[email protected]","Primary"]]},"CVE-2020-0022":{"advisories":[["https://source.android.com/security/bulletin/2020-02-01",["Vendor Advisory","Patch"]],["http://packetstormsecurity.com/files/156891/Android-Bluetooth-Remote-Denial-Of-Service.html",["Third Party Advisory","Exploit"]],["http://seclists.org/fulldisclosure/2020/Feb/10",["Third PLine truncated
|
||||
@@ -1 +1 @@
|
||||
{"CVE-2025-0001":{"cvss":[["3.1",6.5,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","[email protected]","Secondary"]]},"CVE-2025-0009":{"cvss":[["3.1",5.5,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","[email protected]","Secondary"]]},"CVE-2025-0010":{"cvss":[["3.1",6.1,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:H","[email protected]","Secondary"]]},"CVE-2025-0011":{"cvss":[["3.1",3.3,"LOW","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","[email protected]","Secondary"]]},"CVE-2025-0015":{"advisories":[["https://developer.arm.com/Arm%20Security%20Center/Mali%20GPU%20Driver%20Vulnerabilities",["Vendor Advisory"]]],"cvss":[["3.1",7.8,"HIGH","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2025-0032":{"cvss":[["3.1",7.2,"HIGH","CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N","[email protected]","Secondary"]]},"CVE-2025-0034":{"cvss":[["3.1",4.7,"MEDIUM","CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H","[email protected]","Secondary"]]},"CVE-2025-0050":{"advisories":[["https://developer.arm.com/documentation/110435/latest",["Vendor Advisory"]]],"cvss":[["3.1",5.9,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2025-0054":{"cvss":[["3.1",5.4,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","[email protected]","Secondary"]]},"CVE-2025-0072":{"advisories":[["https://developer.arm.com/documentation/110465/latest",["Vendor Advisory"]]],"cvss":[["3.1",7.8,"HIGH","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"],["3.1",7.8,"HIGH","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2025-0074":{"advisories":[["https://source.android.com/security/bulletin/2025-03-01",["Vendor Advisory"]],["https://android.googlesource.com/platform/packages/modules/Bluetooth/+/37bcf769c1aa8dfa8e5524858d47f6a80b765fa4",["Product"]]],"cvss":[["3.1",9.8,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2025-0075":{"advisories":[["https://source.android.com/security/bulletin/2025-03-01",["Vendor Advisory"]],["https://android.googlesource.com/platform/packages/modules/Bluetooth/+/5959f8bcf4efe924b0ba4dbcbfe83e602f0eb0ac",["Product"]]],"cvss":[["3.1",9.8,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2025-0076":{"advisories":[["https://source.android.com/security/bulletin/2025-09-01",["Vendor Advisory"]],["https://android.googlesource.com/platform/frameworks/base/+/d6ad7f34eaf5f0452b93a650265ee432288c0978",["Patch","Product"]]],"cvss":[["3.1",3.3,"LOW","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2025-0086":{"advisories":[["https://source.android.com/security/bulletin/2025-03-01",["Vendor Advisory"]],["https://android.googlesource.com/platform/frameworks/base/+/c1aa9e662464b8fa49765d53a82efa8e06bb176a",["Product"]]],"cvss":[["3.1",6.2,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2025-0087":{"advisories":[["https://source.android.com/security/bulletin/2025-05-01",["Vendor Advisory"]],["https://android.googlesource.com/platform/frameworks/base/+/4c269d7b0ec71951f773844b2a325e556f982a9c",["Product"]]],"cvss":[["3.1",5.1,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2025-0107":{"advisories":[["https://security.paloaltonetworks.com/PAN-SA-2025-0001",["Vendor Advisory"]]],"cvss":[["4.0",7.7,"HIGH","CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:C/RE:H/U:Green","[email protected]","Secondary"],["3.1",9.8,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"]]},"CVE-2025-0108":{"advisories":[["https://security.paloaltonetworks.com/CVE-2025-0108",["Vendor Advisory","Exploit"]],["https://github.com/iSee857/CVE-2025-0108-PoC",["Third Party Advisory","Exploit"]],["https://www.bleepingcomputer.com/news/security/palo-alto-networks-tags-new-firewall-bug-as-exploited-in-attacks",["Third Party Advisory"]],["https://www.darkreading.com/remote-workforce/patch-now-cisa-researchers-warn-palo-alto-flaw-exploited-wild",["Third Party Advisory"]],["https://www.securityweek.com/palo-alto-networks-confirms-exploitation-of-firewall-vulnerability",["Third Party Advisory"]],["https://www.theregister.com/2025/02/19/palo_alto_firewall_attack",["Third Party Advisory"]]],"cvss":[["4.0",8.8,"HIGH","CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:C/RE:M/U:Red","[email protected]","Secondary"],["3.1",9.1,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","nvd@nLine truncated
|
||||
{"CVE-2025-0001":{"cvss":[["3.1",6.5,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","[email protected]","Secondary"]]},"CVE-2025-0009":{"cvss":[["3.1",5.5,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","[email protected]","Secondary"]]},"CVE-2025-0010":{"cvss":[["3.1",6.1,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:H","[email protected]","Secondary"]]},"CVE-2025-0011":{"cvss":[["3.1",3.3,"LOW","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","[email protected]","Secondary"]]},"CVE-2025-0015":{"advisories":[["https://developer.arm.com/Arm%20Security%20Center/Mali%20GPU%20Driver%20Vulnerabilities",["Vendor Advisory"]]],"cvss":[["3.1",7.8,"HIGH","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2025-0032":{"cvss":[["3.1",7.2,"HIGH","CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N","[email protected]","Secondary"]]},"CVE-2025-0034":{"cvss":[["3.1",4.7,"MEDIUM","CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H","[email protected]","Secondary"]]},"CVE-2025-0050":{"advisories":[["https://developer.arm.com/documentation/110435/latest",["Vendor Advisory"]]],"cvss":[["3.1",5.9,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2025-0054":{"cvss":[["3.1",5.4,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","[email protected]","Secondary"]]},"CVE-2025-0072":{"advisories":[["https://developer.arm.com/documentation/110465/latest",["Vendor Advisory"]]],"cvss":[["3.1",7.8,"HIGH","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"],["3.1",7.8,"HIGH","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2025-0074":{"advisories":[["https://source.android.com/security/bulletin/2025-03-01",["Vendor Advisory"]],["https://android.googlesource.com/platform/packages/modules/Bluetooth/+/37bcf769c1aa8dfa8e5524858d47f6a80b765fa4",["Product"]]],"cvss":[["3.1",9.8,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2025-0075":{"advisories":[["https://source.android.com/security/bulletin/2025-03-01",["Vendor Advisory"]],["https://android.googlesource.com/platform/packages/modules/Bluetooth/+/5959f8bcf4efe924b0ba4dbcbfe83e602f0eb0ac",["Product"]]],"cvss":[["3.1",9.8,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2025-0076":{"advisories":[["https://source.android.com/security/bulletin/2025-09-01",["Vendor Advisory"]],["https://android.googlesource.com/platform/frameworks/base/+/d6ad7f34eaf5f0452b93a650265ee432288c0978",["Patch","Product"]]],"cvss":[["3.1",3.3,"LOW","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2025-0086":{"advisories":[["https://source.android.com/security/bulletin/2025-03-01",["Vendor Advisory"]],["https://android.googlesource.com/platform/frameworks/base/+/c1aa9e662464b8fa49765d53a82efa8e06bb176a",["Product"]]],"cvss":[["3.1",6.2,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2025-0087":{"advisories":[["https://source.android.com/security/bulletin/2025-05-01",["Vendor Advisory"]],["https://android.googlesource.com/platform/frameworks/base/+/4c269d7b0ec71951f773844b2a325e556f982a9c",["Product"]]],"cvss":[["3.1",5.1,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2025-0107":{"advisories":[["https://security.paloaltonetworks.com/PAN-SA-2025-0001",["Vendor Advisory"]]],"cvss":[["4.0",7.7,"HIGH","CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:C/RE:H/U:Green","[email protected]","Secondary"],["3.1",9.8,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"]]},"CVE-2025-0108":{"advisories":[["https://security.paloaltonetworks.com/CVE-2025-0108",["Vendor Advisory","Exploit"]],["https://github.com/iSee857/CVE-2025-0108-PoC",["Third Party Advisory","Exploit"]],["https://www.bleepingcomputer.com/news/security/palo-alto-networks-tags-new-firewall-bug-as-exploited-in-attacks",["Third Party Advisory"]],["https://www.darkreading.com/remote-workforce/patch-now-cisa-researchers-warn-palo-alto-flaw-exploited-wild",["Third Party Advisory"]],["https://www.securityweek.com/palo-alto-networks-confirms-exploitation-of-firewall-vulnerability",["Third Party Advisory"]],["https://www.theregister.com/2025/02/19/palo_alto_firewall_attack",["Third Party Advisory"]]],"cvss":[["4.0",8.8,"HIGH","CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:C/RE:M/U:Red","[email protected]","Secondary"],["3.1",9.1,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","nvd@nLine truncated
|
||||
@@ -1 +1 @@
|
||||
{"CVE-2026-0006":{"cvss":[["3.1",9.8,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2026-0013":{"cvss":[["3.1",8.4,"HIGH","CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2026-0023":{"cvss":[["3.1",7.8,"HIGH","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"],["3.1",7.8,"HIGH","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2026-0047":{"cvss":[["3.1",8.4,"HIGH","CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2026-0049":{"advisories":[["https://source.android.com/docs/security/bulletin/2026/2026-04-01",["Vendor Advisory"]]],"cvss":[["3.1",6.2,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2026-0059":{"advisories":[["https://source.android.com/docs/security/bulletin/2026/2026-06-01",["Vendor Advisory"]]],"cvss":[["3.1",8.0,"HIGH","CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2026-0073":{"advisories":[["https://source.android.com/docs/security/bulletin/2026/2026-05-01",["Vendor Advisory"]]],"cvss":[["3.1",8.8,"HIGH","CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2026-0092":{"advisories":[["https://source.android.com/docs/security/bulletin/android-17",["Vendor Advisory"]]],"cvss":[["4.0",10.0,"CRITICAL","CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","[email protected]","Secondary"]]},"CVE-2026-0163":{"cvss":[["3.1",9.8,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2026-0227":{"advisories":[["https://security.paloaltonetworks.com/CVE-2026-0227",["Vendor Advisory"]]],"cvss":[["4.0",6.6,"MEDIUM","CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:U/V:D/RE:M/U:Amber","[email protected]","Secondary"],["3.1",7.5,"HIGH","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","[email protected]","Primary"]]},"CVE-2026-0257":{"advisories":[["https://security.paloaltonetworks.com/CVE-2026-0257",["Vendor Advisory"]],["https://cert-portal.siemens.com/productcert/html/ssa-967325.html",["Third Party Advisory"]]],"cvss":[["4.0",7.8,"HIGH","CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:N/E:A/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:A/V:D/RE:M/U:Red","[email protected]","Secondary"],["3.1",9.1,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","[email protected]","Primary"]]},"CVE-2026-0265":{"advisories":[["https://security.paloaltonetworks.com/CVE-2026-0265",["Vendor Advisory"]],["https://cert-portal.siemens.com/productcert/html/ssa-967325.html",["Third Party Advisory"]]],"cvss":[["4.0",7.2,"HIGH","CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:D/RE:M/U:Red","[email protected]","Secondary"],["3.1",8.1,"HIGH","CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"]]},"CVE-2026-0273":{"advisories":[["https://security.paloaltonetworks.com/CVE-2026-0273",["Vendor Advisory"]]],"cvss":[["4.0",6.1,"MEDIUM","CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:D/RE:M/U:Amber","[email protected]","Secondary"],["3.1",7.2,"HIGH","CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"]]},"CVE-2026-0300":{"advisories":[["https://security.paloaltonetworks.com/CVE-2026-0300",["Vendor Advisory","Mitigation"]],["https://cert-portal.siemens.com/productcert/html/ssa-967325.html",["Third Party Advisory"]]],"cvss":[["4.0",9.3,"CRITICAL","CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N/E:A/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:U/V:C/RE:M/U:Red","[email protected]","Secondary"],["3.1",9.8,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"]]},"CVE-2026-0542":{"cvss":[["4.0",9.2,"CRITICAL","CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","[email protected]","Secondary"]]},"CVE-2026-0544":{"advisories":[["https://github.com/ltranquility/CVE/issues/31",["Third Party Advisory","Issue Tracking","Exploit"]],["https://vuldb.com/?id.339331",["Third Party Advisory"]],["https://vuldb.com/?submit.728909",["Third Party Advisory"Line truncated
|
||||
{"CVE-2026-0006":{"cvss":[["3.1",9.8,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2026-0013":{"cvss":[["3.1",8.4,"HIGH","CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2026-0023":{"cvss":[["3.1",7.8,"HIGH","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"],["3.1",7.8,"HIGH","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2026-0047":{"cvss":[["3.1",8.4,"HIGH","CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2026-0049":{"advisories":[["https://source.android.com/docs/security/bulletin/2026/2026-04-01",["Vendor Advisory"]]],"cvss":[["3.1",6.2,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2026-0059":{"advisories":[["https://source.android.com/docs/security/bulletin/2026/2026-06-01",["Vendor Advisory"]]],"cvss":[["3.1",8.0,"HIGH","CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2026-0073":{"advisories":[["https://source.android.com/docs/security/bulletin/2026/2026-05-01",["Vendor Advisory"]]],"cvss":[["3.1",8.8,"HIGH","CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2026-0092":{"advisories":[["https://source.android.com/docs/security/bulletin/android-17",["Vendor Advisory"]]],"cvss":[["4.0",10.0,"CRITICAL","CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","[email protected]","Secondary"]]},"CVE-2026-0163":{"cvss":[["3.1",9.8,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2026-0227":{"advisories":[["https://security.paloaltonetworks.com/CVE-2026-0227",["Vendor Advisory"]]],"cvss":[["4.0",6.6,"MEDIUM","CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:U/V:D/RE:M/U:Amber","[email protected]","Secondary"],["3.1",7.5,"HIGH","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","[email protected]","Primary"]]},"CVE-2026-0257":{"advisories":[["https://security.paloaltonetworks.com/CVE-2026-0257",["Vendor Advisory"]],["https://cert-portal.siemens.com/productcert/html/ssa-967325.html",["Third Party Advisory"]]],"cvss":[["4.0",7.8,"HIGH","CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:N/E:A/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:A/V:D/RE:M/U:Red","[email protected]","Secondary"],["3.1",9.1,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","[email protected]","Primary"]]},"CVE-2026-0265":{"advisories":[["https://security.paloaltonetworks.com/CVE-2026-0265",["Vendor Advisory"]],["https://cert-portal.siemens.com/productcert/html/ssa-967325.html",["Third Party Advisory"]]],"cvss":[["4.0",7.2,"HIGH","CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:D/RE:M/U:Red","[email protected]","Secondary"],["3.1",8.1,"HIGH","CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"]]},"CVE-2026-0273":{"advisories":[["https://security.paloaltonetworks.com/CVE-2026-0273",["Vendor Advisory"]]],"cvss":[["4.0",6.1,"MEDIUM","CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:D/RE:M/U:Amber","[email protected]","Secondary"],["3.1",7.2,"HIGH","CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"]]},"CVE-2026-0300":{"advisories":[["https://security.paloaltonetworks.com/CVE-2026-0300",["Vendor Advisory","Mitigation"]],["https://cert-portal.siemens.com/productcert/html/ssa-967325.html",["Third Party Advisory"]]],"cvss":[["4.0",9.3,"CRITICAL","CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N/E:A/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:U/V:C/RE:M/U:Red","[email protected]","Secondary"],["3.1",9.8,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"]]},"CVE-2026-0542":{"cvss":[["4.0",9.2,"CRITICAL","CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","[email protected]","Secondary"]]},"CVE-2026-0544":{"advisories":[["https://github.com/ltranquility/CVE/issues/31",["Third Party Advisory","Issue Tracking","Exploit"]],["https://vuldb.com/?id.339331",["Third Party Advisory"]],["https://vuldb.com/?submit.728909",["Third Party Advisory"Line truncated
|
||||
@@ -117065,3 +117065,45 @@ CVE-2026-86674 - https://github.com/ningzichun/student-management-system/issues/
|
||||
CVE-2026-86675 - https://github.com/ltranquility/submit_repository/issues/12
|
||||
CVE-2026-86716 - https://github.com/cesanta/mjs/issues/324
|
||||
CVE-2026-86808 - https://github.com/moltis-org/moltis/issues/1177
|
||||
CVE-2026-12259 - https://github.com/advisories/GHSA-5wp5-5229-5g6q
|
||||
CVE-2026-49114 - https://github.com/advisories/GHSA-q56x-g2fj-4rj6
|
||||
CVE-2026-60004 - https://github.com/advisories/GHSA-rcr6-4jqh-j84m
|
||||
CVE-2026-62383 - https://github.com/advisories/GHSA-3hhw-38pf-pxj6
|
||||
CVE-2026-62384 - https://github.com/advisories/GHSA-f833-7jw8-xwrv
|
||||
CVE-2026-62385 - https://github.com/advisories/GHSA-568f-pv23-39p4
|
||||
CVE-2026-65915 - https://github.com/advisories/GHSA-72r2-7mfr-5xr9
|
||||
CVE-2026-67321 - https://github.com/advisories/GHSA-hcpx-6fm6-wx23
|
||||
CVE-2026-67322 - https://github.com/advisories/GHSA-rwj8-pgh3-r573
|
||||
CVE-2026-67323 - https://github.com/advisories/GHSA-956x-8gvw-wg5v
|
||||
CVE-2026-68584 - https://github.com/advisories/GHSA-7j72-f6wg-cxw6
|
||||
CVE-2026-69222 - https://github.com/advisories/GHSA-4r6h-5v86-94p3
|
||||
CVE-2026-70626 - https://github.com/advisories/GHSA-r6gq-whwq-mvg9
|
||||
CVE-2026-72789 - https://github.com/advisories/GHSA-v684-q882-jgmq
|
||||
CVE-2026-72790 - https://github.com/advisories/GHSA-74pj-6g7r-j55c
|
||||
CVE-2026-73087 - https://github.com/advisories/GHSA-p2w3-6x73-2f6x
|
||||
CVE-2026-73262 - https://github.com/advisories/GHSA-c2jg-2778-ggm4
|
||||
CVE-2026-75596 - https://github.com/advisories/GHSA-fccg-mwvh-qqg4
|
||||
CVE-2026-76217 - https://github.com/advisories/GHSA-hh9p-6wh2-4mfc
|
||||
CVE-2026-76220 - https://github.com/advisories/GHSA-wvpp-8hx9-p66j
|
||||
CVE-2026-76222 - https://github.com/advisories/GHSA-hmq2-w58f-27jc
|
||||
CVE-2026-78675 - https://github.com/advisories/GHSA-7833-fr7j-v32q
|
||||
CVE-2026-78676 - https://github.com/advisories/GHSA-284h-m62q-gf8w
|
||||
CVE-2026-78677 - https://github.com/advisories/GHSA-8mcc-hrx5-hvxc
|
||||
CVE-2026-78682 - https://github.com/advisories/GHSA-6ww7-3frv-cqxh
|
||||
CVE-2026-78683 - https://github.com/advisories/GHSA-rhp5-r9x4-f5g2
|
||||
CVE-2026-79657 - https://github.com/advisories/GHSA-x99w-6fgc-pmfw
|
||||
CVE-2026-79674 - https://github.com/advisories/GHSA-3gq4-3j92-5w49
|
||||
CVE-2026-79676 - https://github.com/advisories/GHSA-p4rw-rvv2-7xwr
|
||||
CVE-2026-81725 - https://github.com/advisories/GHSA-8mpw-7fpc-4gqj
|
||||
CVE-2026-83605 - https://github.com/advisories/GHSA-4w3w-2rp5-g8jm
|
||||
CVE-2026-83606 - https://github.com/advisories/GHSA-g53g-w8rj-fmg7
|
||||
CVE-2026-83607 - https://github.com/advisories/GHSA-w2rr-34g9-rvrj
|
||||
CVE-2026-83608 - https://github.com/advisories/GHSA-27p8-2357-5qqv
|
||||
CVE-2026-83612 - https://github.com/advisories/GHSA-6mj3-qw4j-hgrw
|
||||
CVE-2026-83613 - https://github.com/advisories/GHSA-8344-3jmq-59r6
|
||||
CVE-2026-83614 - https://github.com/advisories/GHSA-93r5-fhx6-vmg9
|
||||
CVE-2026-83615 - https://github.com/advisories/GHSA-965w-775f-mr7g
|
||||
CVE-2026-83616 - https://github.com/advisories/GHSA-c7q8-3ch8-vqpv
|
||||
CVE-2026-83617 - https://github.com/advisories/GHSA-jxjr-3g7g-3944
|
||||
CVE-2026-83618 - https://github.com/advisories/GHSA-vr34-hp96-76pp
|
||||
CVE-2026-84372 - https://github.com/advisories/GHSA-w6f5-v2h6-g786
|
||||
Reference in new issue
Block a user