Sync CVE metadata 2026-09-23

This commit is contained in:
CVE-BOT committed 2026-09-23 08:31:02 +00:00
1 parent 52c3a6d2d0
commit 26e78847c9
54 files changed
+830 -19

No files matched your search

+2 -2
View File
@@ -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=172592-83294-1202" alt="PoC Index" width="100%"></a>
<a href="https://pocindex.io/"><img src="https://raw.githubusercontent.com/0xMarcio/pocindex/main/docs/hero.svg?v=172634-83336-1204" alt="PoC Index" width="100%"></a>
[![last sync](https://img.shields.io/badge/last%20sync-23%20Sep%202026%2008%3A07%20UTC-2f81f7?style=flat-square&labelColor=161b22)](https://github.com/0xMarcio/pocindex/commits/main)&nbsp;[![CI](https://img.shields.io/github/actions/workflow/status/0xMarcio/pocindex/hot_cves.yml?style=flat-square&label=CI&color=2f81f7&labelColor=161b22&_=202609230807)](https://github.com/0xMarcio/pocindex/actions/workflows/hot_cves.yml)&nbsp;[![CVEs with PoCs](https://img.shields.io/badge/CVEs%20with%20PoCs-83%2C294-2f81f7?style=flat-square&labelColor=161b22)](https://pocindex.io/)&nbsp;[![known exploited](https://img.shields.io/badge/known%20exploited-1%2C202-f85149?style=flat-square&labelColor=161b22)](https://pocindex.io/)&nbsp;[![stars](https://img.shields.io/github/stars/0xMarcio/pocindex?style=flat-square&label=stars&color=e3b341&labelColor=161b22&_=202609230807)](https://github.com/0xMarcio/pocindex/stargazers)
[![last sync](https://img.shields.io/badge/last%20sync-23%20Sep%202026%2008%3A07%20UTC-2f81f7?style=flat-square&labelColor=161b22)](https://github.com/0xMarcio/pocindex/commits/main)&nbsp;[![CI](https://img.shields.io/github/actions/workflow/status/0xMarcio/pocindex/hot_cves.yml?style=flat-square&label=CI&color=2f81f7&labelColor=161b22&_=202609230807)](https://github.com/0xMarcio/pocindex/actions/workflows/hot_cves.yml)&nbsp;[![CVEs with PoCs](https://img.shields.io/badge/CVEs%20with%20PoCs-83%2C336-2f81f7?style=flat-square&labelColor=161b22)](https://pocindex.io/)&nbsp;[![known exploited](https://img.shields.io/badge/known%20exploited-1%2C204-f85149?style=flat-square&labelColor=161b22)](https://pocindex.io/)&nbsp;[![stars](https://img.shields.io/github/stars/0xMarcio/pocindex?style=flat-square&label=stars&color=e3b341&labelColor=161b22&_=202609230807)](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>
+19
View File
@@ -0,0 +1,19 @@
### [CVE-2026-56682](https://www.cve.org/CVERecord?id=CVE-2026-56682)
**9Router: Login Brute-Force Lockout Bypass via Spoofable X-9r-Real-Ip Header**
![](https://img.shields.io/static/v1?label=Vendor&message=decolua&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=9router&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%200.5.6&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-307%3A%20Improper%20Restriction%20of%20Excessive%20Authentication%20Attempts&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-807%3A%20Reliance%20on%20Untrusted%20Inputs%20in%20a%20Security%20Decision&color=brightgreen)
### Description
9Router is an AI router & token saver. Prior to 0.5.6, 9Router deployments that allow requests to reach Next.js without the sanitizing custom-server.js wrapper use the client-supplied X-9r-Real-Ip value as the bucket key in getClientIp, checkLock, and recordFail in src/lib/auth/loginLimiter.js for POST /api/auth/login. A remote unauthenticated attacker can rotate the header on every password guess so each request uses a new failed-attempt bucket and the five-attempt progressive lockout never returns HTTP 429. This permits unthrottled password guessing against the dashboard login and can lead to an administrative session if the password is recovered. This issue is fixed in version 0.5.6.
### POC
#### Reference
- https://github.com/advisories/GHSA-32gc-64m7-hj7v
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-58268](https://www.cve.org/CVERecord?id=CVE-2026-58268)
**SIPGO: DoS via unvalidated Content-Length in the stream parser**
![](https://img.shields.io/static/v1?label=Vendor&message=emiago&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=sipgo&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%201.4.1&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-789%3A%20Memory%20Allocation%20with%20Excessive%20Size%20Value&color=brightgreen)
### Description
SIPGO is a library for writing SIP services in the GO language. Prior to 1.4.1, ParserStream.parseSingle in sip/parser_stream.go allocates a SIP body buffer from the client-controlled Content-Length header before ParseMaxMessageLength is enforced. An unauthenticated peer can send a stream-transport message over TCP, TLS, WS, or WSS with an oversized declared length, causing excessive memory allocation and denial of service before the body is read. This issue is fixed in version 1.4.1.
### POC
#### Reference
- https://github.com/advisories/GHSA-pg59-5vwg-4jxq
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-58270](https://www.cve.org/CVERecord?id=CVE-2026-58270)
**Sync-in Server has a ReDoS via Unsanitized Regex in Sync Diff `pathFilters`**
![](https://img.shields.io/static/v1?label=Vendor&message=Sync-in&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=server&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%202.4.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-1333%3A%20Inefficient%20Regular%20Expression%20Complexity&color=brightgreen)
### Description
Sync-in Server is an open-source platform for file storage, sharing, collaboration, and syncing. Prior to version 2.4.0, the sync diff endpoint compiles a user-supplied string into a `RegExp` with no complexity validation. A catastrophic-backtracking pattern (e.g. `^(a+)+b`) blocks the Node.js event loop, making the entire server unresponsive to all users until the container is restarted. Version 2.4.0 patches the issue.
### POC
#### Reference
- https://github.com/advisories/GHSA-jx63-h26r-8cph
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-58271](https://www.cve.org/CVERecord?id=CVE-2026-58271)
**@sync-in/server vulnerable to TOTP Brute-Force via `POST /api/app/sync/register`**
![](https://img.shields.io/static/v1?label=Vendor&message=Sync-in&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=server&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%202.4.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-307%3A%20Improper%20Restriction%20of%20Excessive%20Authentication%20Attempts&color=brightgreen)
### Description
Sync-in Server is an open-source platform for file storage, sharing, collaboration, and syncing. Prior to version 2.4.0, `POST /api/app/sync/register` accepts credentials and a TOTP code to register a desktop sync client. On a failed TOTP, `SyncClientsManager.register()` calls `updateAccesses(user, ip, false)`, which hits a freeze branch that writes `passwordAttempts` back unchanged. The counter never reaches `USER_MAX_PASSWORD_ATTEMPTS` (10) and the lockout gate never fires. A successful guess returns a `{clientId, clientToken}` pair. The token can be exchanged via `POST /api/app/sync/auth/cookie` for a full JWT. While the code is valid, the attacker can also call `POST /api/auth/2fa/disable` to permanently remove MFA. Version 2.4.0 patches the issue.
### POC
#### Reference
- https://github.com/advisories/GHSA-274f-6w77-8qm9
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-59168](https://www.cve.org/CVERecord?id=CVE-2026-59168)
**Dasel: Unbounded recursion in JSON and XML readers causes unrecoverable stack-overflow DoS**
![](https://img.shields.io/static/v1?label=Vendor&message=TomWright&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=dasel&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3E%3D%203.0.0%2C%20%3C%203.11.1&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-674%3A%20Uncontrolled%20Recursion&color=brightgreen)
### Description
Dasel is a command-line tool and library for querying, modifying, and transforming data structures. From 3.0.0 until 3.11.1, parsing/json/json_reader.go decodeValue, decodeObject, and decodeArray, and parsing/xml/reader.go parseElement, recurse once per input nesting level without a depth guard. Deeply nested attacker-controlled JSON or XML supplied through parsing.Format(...).NewReader(...).Read(data), the command-line interface, or the parse selector function can exhaust the Go goroutine stack and raise an unrecoverable fatal error that terminates the entire process. The XML input-size limit does not prevent depth exhaustion, and defer or recover cannot intercept the failure. This issue is fixed in version 3.11.1.
### POC
#### Reference
- https://github.com/advisories/GHSA-cqxr-jxr2-85pq
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-59991](https://www.cve.org/CVERecord?id=CVE-2026-59991)
**psd-tools: Uncontrolled memory allocation in psd-tools composite/numpy via crafted PSD geometry**
![](https://img.shields.io/static/v1?label=Vendor&message=psd-tools&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=psd-tools&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%201.17.4&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-789%3A%20Memory%20Allocation%20with%20Excessive%20Size%20Value&color=brightgreen)
### Description
psd-tools is a Python package for working with Adobe Photoshop PSD files. Prior to 1.17.4, PSDImage.composite() and PSDImage.numpy() allocated output buffers from attacker-controlled PSD header geometry, including width, height, channels, depth, and per-layer rectangles, before validating those values against the available file data. A tiny crafted PSD could therefore cause multi-gigabyte memory allocation, and PSDImage.composite() could return a black image with only a warning instead of raising an exception. Services that composite untrusted PSD files could be terminated by out-of-memory handling. This issue is fixed in version 1.17.4.
### POC
#### Reference
- https://github.com/advisories/GHSA-8q6g-vjhf-jp8m
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-61612](https://www.cve.org/CVERecord?id=CVE-2026-61612)
**@aborruso/ckan-mcp-server has SSRF via DNS-name → internal IP — incomplete fix of CVE-2026-53509**
![](https://img.shields.io/static/v1?label=Vendor&message=ondata&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=ckan-mcp-server&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%40aborruso%2Fckan-mcp-server&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-918%3A%20Server-Side%20Request%20Forgery%20%28SSRF%29&color=brightgreen)
### Description
CKAN MCP Server is a tool for querying CKAN open data portals. Prior to version 0.4.108, the SSRF guard `validateServerUrl` (added for CVE-2026-33060, extended for CVE-2026-53509) validates only the hostname string and never resolves DNS. Any caller-supplied `server_url` whose hostname *resolves* to an internal address passes the guard, so the server issues requests to loopback and cloud metadata (`169.254.169.254`). This is a third bypass of the same guard, and it reaches IMDS — strictly more than CVE-2026-53509, which only reached loopback. Version 0.4.108 contains an updated fix.
### POC
#### Reference
- https://github.com/advisories/GHSA-798p-78g2-v556
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-62985](https://www.cve.org/CVERecord?id=CVE-2026-62985)
**request-filtering-agent: Synchronous throw from createConnection() for literal private-IP hosts bypasses req.on('error'), crashing the Node.js process**
![](https://img.shields.io/static/v1?label=Vendor&message=azu&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=request-filtering-agent&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%203.2.1&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-248%3A%20Uncaught%20Exception&color=brightgreen)
### Description
request-filtering-agent is an http(s).Agent implementation that blocks requests to Private/Reserved IP addresses. Prior to 3.2.1, RequestFilteringHttpAgent and RequestFilteringHttpsAgent synchronously threw from createConnection when rejecting a literal private-IP host such as 169.254.169.254 or 127.0.0.1. Because Node.js http.request and http.get expect connection failures to be delivered asynchronously, the throw bypassed req.on('error') and became an uncaught exception that could terminate the application process. Hostnames resolved through the asynchronous lookup path were not affected by this error-delivery asymmetry. This issue is fixed in version 3.2.1.
### POC
#### Reference
- https://github.com/advisories/GHSA-r3r9-wp5j-pq5g
#### Github
No PoCs found on GitHub currently.
+19
View File
@@ -0,0 +1,19 @@
### [CVE-2026-62987](https://www.cve.org/CVERecord?id=CVE-2026-62987)
**Fabio - Incomplete fix for CVE-2025-48865: operator-configured trust headers (clientip/tls/requestid) still strippable via the Connection header**
![](https://img.shields.io/static/v1?label=Vendor&message=fabiolb&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=fabio&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3E%3D%201.6.6%2C%20%3C%201.7.2&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-290%3A%20Authentication%20Bypass%20by%20Spoofing&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-348%3A%20Use%20of%20Less%20Trusted%20Source&color=brightgreen)
### Description
Fabio is an HTTP(S) and TCP router for deploying applications managed by consul. From 1.6.6 until 1.7.2, the CVE-2025-48865 fix in proxy/http_headers.go uses protectHeaders for a hardcoded set of forwarded headers but omits the operator-configured ClientIPHeader, TLSHeader, and RequestID names. In proxy/http_proxy.go, HTTPProxy.ServeHTTP calls addHeaders to set these trust headers before Go ReverseProxy processes the inbound Connection header, allowing an unauthenticated client to name and remove the configured headers before the request reaches the backend. Deployments that enable the corresponding proxy.header options can therefore lose client-IP, TLS-termination, or request-correlation signals used by backend authorization and auditing; the options are empty by default, and the hardcoded protected forwarded headers are unaffected. This issue is fixed in version 1.7.2.
### POC
#### Reference
- https://github.com/advisories/GHSA-fq95-v8xc-jm3v
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-63627](https://www.cve.org/CVERecord?id=CVE-2026-63627)
**mppx: Gas Draining with padding**
![](https://img.shields.io/static/v1?label=Vendor&message=wevm&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=mppx&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%200.8.2&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-20%3A%20Improper%20Input%20Validation&color=brightgreen)
### Description
mppx is a TypeScript interface for machine payments protocol. Prior to 0.8.2, FeePayerPolicy in src/tempo/internal/fee-payer.ts used decodeFunctionData to validate fee-sponsored calldata but did not reject trailing bytes. A client could append nonzero padding that increased intrinsic calldata gas while gas_limit and max_fee_per_gas remained within policy caps, causing the server fee_payer wallet to pay substantially more than the decoded transaction required. The tested 16 KB header limit bounded the demonstrated padding to about 5,500 bytes and produced approximately five times the normal transaction fee. This issue is fixed in version 0.8.2.
### POC
#### Reference
- https://github.com/advisories/GHSA-727h-3vm5-qwq6
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-63628](https://www.cve.org/CVERecord?id=CVE-2026-63628)
**mppx: Gas Draining with access list**
![](https://img.shields.io/static/v1?label=Vendor&message=wevm&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=mppx&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%200.8.2&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-20%3A%20Improper%20Input%20Validation&color=brightgreen)
### Description
mppx is a TypeScript interface for machine payments protocol. Prior to 0.8.2, the fee-payer cosigning path in src/tempo/internal/fee-payer.ts copied a client-supplied access_list from a 0x78 FeePayerEnvelope without validating its length or contents. Because EIP-2930 access-list entries consume intrinsic gas even when the listed addresses are never used, a client could add fabricated address-only entries and cause the server fee_payer wallet to pay unnecessary transaction fees. The demonstrated 180-entry list remained within the 500,000 gas policy cap, 16 KB header limit, and RPC simulation budget while increasing the fee by approximately 9.4 times. This issue is fixed in version 0.8.2.
### POC
#### Reference
- https://github.com/advisories/GHSA-vc9j-9wph-qghj
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-75510](https://www.cve.org/CVERecord?id=CVE-2026-75510)
**Novu: Stored XSS in In-App Inbox via notification redirect.url javascript: scheme**
![](https://img.shields.io/static/v1?label=Vendor&message=novuhq&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=novu&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%203.18.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-79%3A%20Improper%20Neutralization%20of%20Input%20During%20Web%20Page%20Generation%20%28%27Cross-site%20Scripting%27%29&color=brightgreen)
### Description
Novu provides an API for sending notifications through multiple channels. Prior to 3.18.0, Novu's @novu/js In-App Inbox and the @novu/react Inbox component accept a notification call-to-action redirect.url from the v1 cta.data object and pass it through apps/api/src/app/inbox/utils/notification-mapper.ts and packages/js/src/ui/components/Notification/DefaultNotification.tsx to the navigate function in packages/js/src/ui/context/InboxContext.tsx without validating its URL scheme. An authenticated organization member or environment API-key holder can store a javascript: redirect with target _self in an in-app workflow. When a recipient using a Chromium-based browser clicks the notification, window.open executes the redirect in the current inbox-hosting origin, which can expose session material and permit authenticated actions in a customer application or the self-hosted Novu dashboard. This issue is fixed in version 3.18.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-8gr3-5j6f-25gp
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-76909](https://www.cve.org/CVERecord?id=CVE-2026-76909)
**Unleash: CR-approval email renders user-controlled raw HTML**
![](https://img.shields.io/static/v1?label=Vendor&message=Unleash&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=unleash&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%208.0.3&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-79%3A%20Improper%20Neutralization%20of%20Input%20During%20Web%20Page%20Generation%20%28%27Cross-site%20Scripting%27%29&color=brightgreen)
### Description
Unleash is an open-source feature management platform. Prior to 8.0.3, the change-request approval email template at src/mailtemplates/requested-cr-approval/requested-cr-approval.html.mustache renders the user-controlled changeRequestTitle, requesterName, and requesterEmail values without HTML escaping, and sendRequestedCRApprovalEmail passes those values to Mustache rendering. A project member who can create a change request when approval emails are enabled can inject HTML into an approver's notification, allowing forged links, tracking content, or visually altered email content. This issue is fixed in version 8.0.3.
### POC
#### Reference
- https://github.com/advisories/GHSA-7hvx-28gp-mf6j
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-76910](https://www.cve.org/CVERecord?id=CVE-2026-76910)
**Unleash: Clone-feature lets a user copy a feature from a project they cannot read**
![](https://img.shields.io/static/v1?label=Vendor&message=Unleash&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=unleash&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%208.0.3&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-639%3A%20Authorization%20Bypass%20Through%20User-Controlled%20Key&color=brightgreen)
### Description
Unleash is an open-source feature management platform. Prior to 8.0.3, cloneFeatureToggle and POST /api/admin/projects/:projectId/features/:featureName/clone authorize creation in the destination project but do not verify access to the source project. Because feature names are globally unique, a user with create or clone permission in one project who knows or guesses another project's feature name can copy that feature into the authorized project and inspect its strategy parameters, constraints, variants, and variant payloads. This issue is fixed in version 8.0.3.
### POC
#### Reference
- https://github.com/advisories/GHSA-8xcj-9hfr-fh9j
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-77243](https://www.cve.org/CVERecord?id=CVE-2026-77243)
**MCP Atlassian: ENABLED_TOOLS / Toolset authorization bypass**
![](https://img.shields.io/static/v1?label=Vendor&message=sooperset&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=mcp-atlassian&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%200.22.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-862%3A%20Missing%20Authorization&color=brightgreen)
### Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, ENABLED_TOOLS and TOOLSETS are applied when tools are listed but are not rechecked when a tools/call request is dispatched. A client that knows a hidden tool name can directly invoke excluded read, write, or delete tools despite the operator's configured least-privilege restrictions. The advisory traces the vulnerable input and processing flow through ENABLED_TOOLS, TOOLSETS, tools/list, tools/call, and _call_tool_mcp, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-3r68-hf9h-887v
#### Github
No PoCs found on GitHub currently.
+20
View File
@@ -0,0 +1,20 @@
### [CVE-2026-77244](https://www.cve.org/CVERecord?id=CVE-2026-77244)
**[mcp-atlassian] Authentication bypass in HTTP transport: AtlassianOpaqueTokenVerifier accepts any non-empty token**
![](https://img.shields.io/static/v1?label=Vendor&message=sooperset&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=mcp-atlassian&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%200.22.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-287%3A%20Improper%20Authentication&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-303%3A%20Incorrect%20Implementation%20of%20Authentication%20Algorithm&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-862%3A%20Missing%20Authorization&color=brightgreen)
### Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, the HTTP transport accepts requests without a verified user identity and downstream fetcher construction falls back to the operator's globally configured Jira or Confluence credentials. A network client that can reach the MCP endpoint can invoke Atlassian tools as the operator, including read and write operations available to that account. The advisory traces the vulnerable input and processing flow through UserTokenMiddleware, AtlassianOpaqueTokenVerifier, _get_fetcher, and streamable-http, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-wrhw-j3f9-8vc6
#### Github
No PoCs found on GitHub currently.
+20
View File
@@ -0,0 +1,20 @@
### [CVE-2026-77246](https://www.cve.org/CVERecord?id=CVE-2026-77246)
**MCP Atlassian: MCP HTTP Client Server-Local File Exfiltration via Unvalidated Attachment Upload Path**
![](https://img.shields.io/static/v1?label=Vendor&message=sooperset&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=mcp-atlassian&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%200.22.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-22%3A%20Improper%20Limitation%20of%20a%20Pathname%20to%20a%20Restricted%20Directory%20%28%27Path%20Traversal%27%29&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-200%3A%20Exposure%20of%20Sensitive%20Information%20to%20an%20Unauthorized%20Actor&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-441%3A%20Unintended%20Proxy%20or%20Intermediary%20%28%27Confused%20Deputy%27%29&color=brightgreen)
### Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, an HTTP transport deployment with READ_ONLY_MODE=false accepts a request without an Authorization identity and permits attacker-controlled Atlassian service headers, including X-Atlassian-Confluence-Url, to select a public attacker hostname or one allowed by MCP_ALLOWED_URL_DOMAINS. A caller can then invoke confluence_upload_attachment or the Jira attachment variant in src/mcp_atlassian/jira/attachments.py with a server-local file_path and cause the MCP process to send the file to the selected attachment endpoint. This issue is fixed in version 0.22.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-wv8v-v4c5-v75j
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-77247](https://www.cve.org/CVERecord?id=CVE-2026-77247)
**MCP Atlassian: Arbitrary server-local file upload to Jira/Confluence attachments via unrestricted file_path parameters**
![](https://img.shields.io/static/v1?label=Vendor&message=sooperset&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=mcp-atlassian&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%200.22.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-73%3A%20External%20Control%20of%20File%20Name%20or%20Path&color=brightgreen)
### Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, Jira and Confluence upload tools interpret caller-controlled path arguments on the MCP server and open those files before sending them as attachments. In remote or multi-user deployments, a permitted client can disclose host files without shell or direct filesystem access. The advisory traces the vulnerable input and processing flow through AttachmentsMixin.upload_attachment, AttachmentsMixin.upload_attachments, file_path, file_paths, and jira update_issue, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-f6pj-qv47-g96w
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-77249](https://www.cve.org/CVERecord?id=CVE-2026-77249)
**MCP Atlassian: Incomplete fix for CVE-2026-27826: redirect-based SSRF via unhooked requests session in Jira user-permission lookup**
![](https://img.shields.io/static/v1?label=Vendor&message=sooperset&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=mcp-atlassian&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%200.22.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-918%3A%20Server-Side%20Request%20Forgery%20%28SSRF%29&color=brightgreen)
### Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, JiraUserMixin._lookup_user_by_permissions uses the module-level requests.get function instead of the fetcher's protected session. A caller-controlled public Jira URL can redirect that unhooked request to an internal address, bypassing the redirect checks added for CVE-2026-27826. The advisory traces the vulnerable input and processing flow through JiraUserMixin._lookup_user_by_permissions, requests.get, self.jira._session.get, and _make_ssrf_safe_hook, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-v9m3-wfh8-5646
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-77250](https://www.cve.org/CVERecord?id=CVE-2026-77250)
**MCP Atlassian: OAuth fallback token storage writes plaintext access and refresh tokens with group-readable permissions**
![](https://img.shields.io/static/v1?label=Vendor&message=sooperset&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=mcp-atlassian&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%200.22.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-312%3A%20Cleartext%20Storage%20of%20Sensitive%20Information&color=brightgreen)
### Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, OAuthConfig writes a plaintext fallback file containing access and refresh tokens under the user's .mcp-atlassian directory using process-default permissions. On systems with a permissive umask, same-group or other local users and processes can read the persisted tokens and reuse the associated Atlassian access. The advisory traces the vulnerable input and processing flow through OAuthConfig._save_tokens, ~/.mcp-atlassian/oauth-<client_id>.json, access_token, and refresh_token, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-g5xv-mhgm-v5f6
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-77251](https://www.cve.org/CVERecord?id=CVE-2026-77251)
**MCP Atlassian: JIRA_PROJECTS_FILTER / CONFLUENCE_SPACES_FILTER allow forbidden-project content exfiltration (one LIVE-proven on Atlassian Cloud)**
![](https://img.shields.io/static/v1?label=Vendor&message=sooperset&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=mcp-atlassian&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%200.22.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-1276%3A%20Hardware%20Child%20Block%20Incorrectly%20Connected%20to%20Parent%20System&color=brightgreen)
### Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, Jira search accepts a forbidden project clause because it checks only for the presence of project syntax, Confluence search uses an incomplete case-sensitive space check, and Jira board APIs omit project-filter enforcement. These paths expose issues, boards, or pages outside JIRA_PROJECTS_FILTER or CONFLUENCE_SPACES_FILTER when the operator credentials have broader access. The advisory traces the vulnerable input and processing flow through jira_search, confluence_search, get_board_issues, get_agile_boards, JIRA_PROJECTS_FILTER, and CONFLUENCE_SPACES_FILTER, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-w66g-j6c4-hcfc
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-77253](https://www.cve.org/CVERecord?id=CVE-2026-77253)
**MCP Atlassian: Jira and Confluence attachment upload tools can read arbitrary server-local files**
![](https://img.shields.io/static/v1?label=Vendor&message=sooperset&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=mcp-atlassian&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%200.22.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-22%3A%20Improper%20Limitation%20of%20a%20Pathname%20to%20a%20Restricted%20Directory%20%28%27Path%20Traversal%27%29&color=brightgreen)
### Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, Jira and Confluence attachment upload tools accept arbitrary local filesystem paths and send the selected bytes to Atlassian. In HTTP or multi-user deployments, a caller can cross the client-to-server filesystem boundary and disclose configuration, credentials, mounted secrets, or other files readable by the MCP process. The advisory traces the vulnerable input and processing flow through jira_upload_attachment, confluence_upload_attachment, file_path, and server-local filesystem, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-vc25-24vv-fxxm
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-77257](https://www.cve.org/CVERecord?id=CVE-2026-77257)
**MCP Atlassian: HTTP upload tools accept arbitrary server-local file paths**
![](https://img.shields.io/static/v1?label=Vendor&message=sooperset&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=mcp-atlassian&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%200.22.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-22%3A%20Improper%20Limitation%20of%20a%20Pathname%20to%20a%20Restricted%20Directory%20%28%27Path%20Traversal%27%29&color=brightgreen)
### Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, HTTP-exposed Jira and Confluence upload tools pass a caller-provided file_path to local file operations without restricting it to the workspace. A remote MCP caller with tool access can cause the server to read sensitive local files and upload them as Atlassian attachments. The advisory traces the vulnerable input and processing flow through streamable-http, upload_attachment, and file_path, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-mrq8-fv7v-hhjg
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-77258](https://www.cve.org/CVERecord?id=CVE-2026-77258)
**MCP Atlassian: Arbitrary file read/exfiltration via upload_attachment missing validate_safe_path()**
![](https://img.shields.io/static/v1?label=Vendor&message=sooperset&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=mcp-atlassian&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%200.22.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-22%3A%20Improper%20Limitation%20of%20a%20Pathname%20to%20a%20Restricted%20Directory%20%28%27Path%20Traversal%27%29&color=brightgreen)
### Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, upload_attachment in src/mcp_atlassian/confluence/attachments.py accepts a caller-controlled file_path and opens the selected server-local file without restricting it to the workspace. A permitted Confluence MCP caller can upload the file as an attachment and disclose data readable by the server process. This issue is fixed in version 0.22.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-93xw-j965-9mx3
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-77261](https://www.cve.org/CVERecord?id=CVE-2026-77261)
**MCP Atlassian: SSRF redirect protection missing for basic-auth and OAuth authentication branches**
![](https://img.shields.io/static/v1?label=Vendor&message=sooperset&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=mcp-atlassian&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%200.22.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-918%3A%20Server-Side%20Request%20Forgery%20%28SSRF%29&color=brightgreen)
### Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, _make_ssrf_safe_hook is omitted from JiraFetcher and ConfluenceFetcher sessions created through the basic-auth and oauth_pat branches. If an attacker-controlled or compromised configured Atlassian instance returns a redirect to an internal address, those sessions can follow the redirect without revalidating its destination. This issue is fixed in version 0.22.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-6529-c226-h328
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-77262](https://www.cve.org/CVERecord?id=CVE-2026-77262)
**MCP Atlassian: Path Traversal / Arbitrary File Read in confluence_upload_attachment MCP tool (incomplete fix of CVE-2026-27825)**
![](https://img.shields.io/static/v1?label=Vendor&message=sooperset&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=mcp-atlassian&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%200.22.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-22%3A%20Improper%20Limitation%20of%20a%20Pathname%20to%20a%20Restricted%20Directory%20%28%27Path%20Traversal%27%29&color=brightgreen)
### Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, confluence_upload_attachment accepts an attacker-controlled file_path and does not apply the path restriction added for the earlier download vulnerability. A caller can traverse outside the workspace and upload arbitrary server-readable files to Confluence. The advisory traces the vulnerable input and processing flow through confluence_upload_attachment, file_path, and CVE-2026-27825, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-p6hp-93wp-fh6p
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-77266](https://www.cve.org/CVERecord?id=CVE-2026-77266)
**MCP Atlassian: Path traversal in upload_attachment allows arbitrary file read and exfiltration via MCP tool call**
![](https://img.shields.io/static/v1?label=Vendor&message=sooperset&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=mcp-atlassian&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%200.22.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-22%3A%20Improper%20Limitation%20of%20a%20Pathname%20to%20a%20Restricted%20Directory%20%28%27Path%20Traversal%27%29&color=brightgreen)
### Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, upload_attachment accepts absolute paths and traversal sequences without constraining the resolved path to the server workspace. An MCP caller with attachment access can read a chosen server-local file and exfiltrate it through Jira or Confluence. The advisory traces the vulnerable input and processing flow through upload_attachment, file_path, and path traversal, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-mfv2-4wvm-9pgp
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-77267](https://www.cve.org/CVERecord?id=CVE-2026-77267)
**mcp-atlassian has an incomplete SSRF remediation**
![](https://img.shields.io/static/v1?label=Vendor&message=sooperset&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=mcp-atlassian&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%200.22.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-918%3A%20Server-Side%20Request%20Forgery%20%28SSRF%29&color=brightgreen)
### Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, the X-Atlassian-Jira-Url and X-Atlassian-Confluence-Url headers are processed by _process_authentication_headers and used to construct Atlassian fetchers without calling validate_url_for_ssrf. A caller who can set these headers can supply an internal or metadata-service URL and cause the server to send requests to that destination, bypassing the incomplete CVE-2026-27826 remediation. This issue is fixed in version 0.22.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-5wf4-jqxh-8gm3
#### Github
No PoCs found on GitHub currently.
+19
View File
@@ -0,0 +1,19 @@
### [CVE-2026-77271](https://www.cve.org/CVERecord?id=CVE-2026-77271)
**MCP Atlassian: Incomplete path traversal fix allows intra-CWD module overwrite and RCE (bypass of CVE-2026-27825)**
![](https://img.shields.io/static/v1?label=Vendor&message=sooperset&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=mcp-atlassian&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%200.22.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-22%3A%20Improper%20Limitation%20of%20a%20Pathname%20to%20a%20Restricted%20Directory%20%28%27Path%20Traversal%27%29&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-94%3A%20Improper%20Control%20of%20Generation%20of%20Code%20%28%27Code%20Injection%27%29&color=brightgreen)
### Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, validate_safe_path defaults its base directory to os.getcwd(), and affected Confluence attachment call sites omit base_dir, allowing attacker-selected writes within the working directory. This Python module overwrite can provide code execution when the application later imports the modified module, bypassing the remediation tracked as CVE-2026-27825. This issue is fixed in version 0.22.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-6vmq-24h2-pj7j
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-77272](https://www.cve.org/CVERecord?id=CVE-2026-77272)
**MCP Atlassian: Reflected XSS in OAuth Setup Callback Handler**
![](https://img.shields.io/static/v1?label=Vendor&message=sooperset&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=mcp-atlassian&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%200.22.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-79%3A%20Improper%20Neutralization%20of%20Input%20During%20Web%20Page%20Generation%20%28%27Cross-site%20Scripting%27%29&color=brightgreen)
### Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, the OAuth error query parameter is passed to CallbackHandler._send_response in oauth_setup.py and interpolated into an HTML page without escaping. A crafted authorization callback can inject markup or script that executes in the browser of a user completing the OAuth flow. This issue is fixed in version 0.22.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-g2r2-3j32-j27x
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-77274](https://www.cve.org/CVERecord?id=CVE-2026-77274)
**MCP Atlassian: SSRF Protection Bypass**
![](https://img.shields.io/static/v1?label=Vendor&message=sooperset&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=mcp-atlassian&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%200.22.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-918%3A%20Server-Side%20Request%20Forgery%20%28SSRF%29&color=brightgreen)
### Description
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, validate_url_for_ssrf has a backslash authority confusion because it interprets the authority differently from the Requests connection layer in the header-based Jira and Confluence URL authentication flow. A crafted URL can validate as an external hostname while the HTTP client connects to an internal host, permitting server-side requests to protected network resources. This issue is fixed in version 0.22.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-hgcf-4mq8-5266
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-77322](https://www.cve.org/CVERecord?id=CVE-2026-77322)
**SIPGO: DoS via unvalidated WebSocket frame length**
![](https://img.shields.io/static/v1?label=Vendor&message=emiago&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=sipgo&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%201.4.3&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-789%3A%20Memory%20Allocation%20with%20Excessive%20Size%20Value&color=brightgreen)
### Description
SIPGO is a library for writing SIP services in the GO language. Prior to 1.4.3, WSConnection.Read in sip/transport_ws.go creates a wsutil.Reader without setting MaxFrameSize, allowing NextFrame to accept a client-controlled header.Length before ParseMaxMessageLength is applied. An unauthenticated WS or WSS peer can send a frame header declaring an extremely large payload, causing an oversized allocation or a makeslice length panic before the payload is read and crashing or exhausting memory in the server process. This issue is fixed in version 1.4.3.
### POC
#### Reference
- https://github.com/advisories/GHSA-8h6x-h86x-75wh
#### Github
No PoCs found on GitHub currently.
+19
View File
@@ -0,0 +1,19 @@
### [CVE-2026-77528](https://www.cve.org/CVERecord?id=CVE-2026-77528)
**Autobahn Python permessage-deflate bypasses maxMessagePayloadSize after inflation**
![](https://img.shields.io/static/v1?label=Vendor&message=crossbario&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=autobahn-python&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%2026.7.1&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-409%3A%20Improper%20Handling%20of%20Highly%20Compressed%20Data%20%28Data%20Amplification%29&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-770%3A%20Allocation%20of%20Resources%20Without%20Limits%20or%20Throttling&color=brightgreen)
### Description
Autobahn Python is a WebSocket and WAMP implementation for Python that supports Twisted and asyncio. Prior to 26.7.1, WebSocket endpoints that accept permessage-deflate and rely on maxMessagePayloadSize enforce that limit against the compressed frame length before inflation but do not recheck the decompressed message size before delivery. A remote unauthenticated client can send a valid compressed frame below the configured wire-size limit that expands beyond the application message limit, causing oversized data to be allocated, joined, validated, and passed to application callbacks. This can create resource-exhaustion pressure, but the advisory does not establish confidentiality or integrity impact. This issue is fixed in version 26.7.1.
### POC
#### Reference
- https://github.com/advisories/GHSA-hxp9-w8x3-p566
#### Github
No PoCs found on GitHub currently.
+20
View File
@@ -0,0 +1,20 @@
### [CVE-2026-77560](https://www.cve.org/CVERecord?id=CVE-2026-77560)
**Tinyauth: forward-auth per-app ACL is matched case-sensitively against the (case-insensitive) hostname, letting an authenticated user reach apps they are not on the allowlist for**
![](https://img.shields.io/static/v1?label=Vendor&message=tinyauthapp&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=tinyauth&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%205.1.2&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-178%3A%20Improper%20Handling%20of%20Case%20Sensitivity&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-636%3A%20Not%20Failing%20Securely%20%28%27Failing%20Open%27%29&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-863%3A%20Incorrect%20Authorization&color=brightgreen)
### Description
Tinyauth is an authentication and authorization server. Prior to 5.1.2, Tinyauth compares forwarded hostnames case-sensitively while reverse proxies route equivalent hostnames case-insensitively, allowing an authenticated low-privilege user to bypass per-app access controls with a differently cased hostname. The lookup in internal/service/access_controls_service.go through lookupStaticACLs and GetAccessControls, and the Docker-label fallback in internal/service/docker_service.go through GetLabels, can miss the configured app and return an empty access-control object. internal/controller/proxy_controller.go proxyHandler then treats the empty user, group, OAuth, LDAP, and IP restrictions as permissive and returns an authenticated result for an app that should exclude the user. Unauthenticated users remain subject to login, and global login-time allowlists are not bypassed. This issue is fixed in version 5.1.2.
### POC
#### Reference
- https://github.com/advisories/GHSA-328g-jx67-v94g
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-77561](https://www.cve.org/CVERecord?id=CVE-2026-77561)
**Tinyauth: Unauthenticated login attempts can trigger global login lockdown denial of service**
![](https://img.shields.io/static/v1?label=Vendor&message=tinyauthapp&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=tinyauth&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%205.1.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-307%3A%20Improper%20Restriction%20of%20Excessive%20Authentication%20Attempts&color=brightgreen)
### Description
Tinyauth is an authentication and authorization server. Prior to 5.1.0, an unauthenticated remote attacker can send POST /api/user/login requests with 257 distinct nonexistent usernames to fill MaxLoginAttemptRecords and activate a global login lockdown. internal/controller/user_controller.go loginHandler passes each attacker-controlled identifier to internal/service/auth_service.go RecordLoginAttempt, which invokes lockdownMode after the map reaches its cap. IsAccountLocked checks that global state before validating unrelated accounts, causing valid users to receive HTTP 429 until auth.loginTimeout expires, approximately 300 seconds by default. The attack can be repeated, but existing authenticated sessions are not invalidated. This issue is fixed in version 5.1.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-9xhm-w3wj-xhqh
#### Github
No PoCs found on GitHub currently.
+20
View File
@@ -0,0 +1,20 @@
### [CVE-2026-79767](https://www.cve.org/CVERecord?id=CVE-2026-79767)
**Gardener: Authorization Bypass via Group Subject Injection**
![](https://img.shields.io/static/v1?label=Vendor&message=gardener&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=gardener&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%201.142.6&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=%3E%3D%201.143.0%2C%20%3C%201.143.3&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=%3E%3D%201.144.0%2C%20%3C%201.144.2&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-863%3A%20Incorrect%20Authorization&color=brightgreen)
### Description
Gardener implements the automated management and operation of Kubernetes clusters as a service. Prior to 1.142.6, 1.143.3, 1.144.2, and 1.145.0, the customverbauthorizer admission plugin's mustCheckProjectMembers manage-members check compares changes to User subjects but does not account for Group or ServiceAccount subjects in Project.spec.members. A project administrator who lacks manage-members permission can add arbitrary Group or ServiceAccount subjects, including the system:authenticated Group, and thereby grant broad project access. The resulting access can include Shoots, Secrets, and cloud provider credentials. This issue is fixed in versions 1.142.6, 1.143.3, 1.144.2, and 1.145.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-gfjv-gqf2-c888
#### Github
No PoCs found on GitHub currently.
+19
View File
@@ -0,0 +1,19 @@
### [CVE-2026-79913](https://www.cve.org/CVERecord?id=CVE-2026-79913)
**Cloudreve: SSRF guard bypass: checkIP does not decode IPv6-transition wrappers (NAT64, IPv4-compatible, 6to4) reaching internal and cloud-metadata addresses**
![](https://img.shields.io/static/v1?label=Vendor&message=cloudreve&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=cloudreve&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%204.18.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-918%3A%20Server-Side%20Request%20Forgery%20%28SSRF%29&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-697%3A%20Incorrect%20Comparison&color=brightgreen)
### Description
Cloudreve is a self-hosted file management and sharing system. Prior to 4.18.0, the ValidateExternalURL server-side request forgery guard in pkg/request/ssrf.go passes resolved addresses to checkIP without decoding NAT64, IPv4-compatible, and 6to4 IPv4-in-IPv6 transition forms. An authenticated user with remote-download access can provide SrcUri through RemoteDownloadTask.createDownloadTask so a wrapper embedding a loopback, private, link-local, or cloud metadata IPv4 address is classified as public and fetched, exposing internal service responses and cloud instance credentials. IPv4-mapped IPv6 addresses remain blocked because Go converts that form with net.IP.To4. This issue is fixed in version 4.18.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-jvh5-97xg-v99f
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-85740](https://www.cve.org/CVERecord?id=CVE-2026-85740)
**LightRAG: SSRF via IPv6-transition address bypass (NAT64, IPv4-compatible, 6to4) of the native-markdown image-download guard**
![](https://img.shields.io/static/v1?label=Vendor&message=HKUDS&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=LightRAG&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%201.5.5&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-918%3A%20Server-Side%20Request%20Forgery%20%28SSRF%29&color=brightgreen)
### Description
LightRAG provides simple and fast retrieval-augmented generation. Prior to 1.5.5, _validated_addresses in lightrag/parser/markdown/parser.py evaluates the literal resolved address with ipaddress.is_global without consistently classifying an IPv4 address embedded in an IPv6 transition wrapper. A caller who can upload a Markdown or textpack document can supply an external image URL using NAT64 64:ff9b::/96 or an IPv4-compatible form that embeds a loopback, private, or cloud-metadata IPv4 address. On a deployment with compatible NAT64 or DNS64 routing, _download and _build_guarded_opener accept the wrapper and fetch the internal resource, whose body is then ingested. Current interpreter behavior already blocks some RFC 8215 and 6to4 forms, but the fixed guard handles all documented wrappers without becoming more permissive than the standard library. This issue is fixed in version 1.5.5.
### POC
#### Reference
- https://github.com/advisories/GHSA-vv3m-f8x4-7377
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-86062](https://www.cve.org/CVERecord?id=CVE-2026-86062)
**LightRAG: Stored Cross-Site Scripting (XSS) in the LightRAG WebUI chat/answer renderer via ingested content**
![](https://img.shields.io/static/v1?label=Vendor&message=HKUDS&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=LightRAG&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%201.5.5&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-79%3A%20Improper%20Neutralization%20of%20Input%20During%20Web%20Page%20Generation%20%28%27Cross-site%20Scripting%27%29&color=brightgreen)
### Description
LightRAG provides simple and fast retrieval-augmented generation. Prior to 1.5.5, lightrag_webui/src/components/retrieval/ChatMessage.tsx renders answer and thinking content with react-markdown, rehypeRaw, and skipHtml=false without an HTML sanitizer. An attacker who can add a document can store raw HTML that is returned through the query path and rendered as active content by MessageMarkdown. A user who later retrieves the content can execute attacker-controlled JavaScript through elements such as an iframe srcdoc; the additional Mermaid securityLevel: loose rendering path also injects generated SVG through innerHTML. The script runs in the LightRAG WebUI origin and can read the API token in localStorage and perform API actions as the victim. This issue is fixed in version 1.5.5.
### POC
#### Reference
- https://github.com/advisories/GHSA-xpjq-3w4w-w5wr
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-88010](https://www.cve.org/CVERecord?id=CVE-2026-88010)
**Traefik: BasicAuth singleflight coalescing reintroduces an unauthenticated username-enumeration timing oracle**
![](https://img.shields.io/static/v1?label=Vendor&message=traefik&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=traefik&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3E%3D%203.6.11%2C%20%3C%203.7.13&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-208%3A%20Observable%20Timing%20Discrepancy&color=brightgreen)
### Description
Traefik is an open source HTTP reverse proxy and load balancer. From 3.6.11 until 3.7.13, checkPassword in pkg/middlewares/auth/basic_auth.go constructs the BasicAuth singleflight key from the submitted password and stored secret. Concurrent requests for absent usernames therefore coalesce on one key while configured usernames perform separate password hashes, creating an unauthenticated timing discrepancy that reveals whether a username exists. Sequential checks remain cost-equalized, Traefik v2 and Digest authentication are not affected, and the issue does not disclose credentials or bypass authentication. This issue is fixed in version 3.7.13.
### POC
#### Reference
- https://github.com/advisories/GHSA-8fcf-v89g-xpg6
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-91129](https://www.cve.org/CVERecord?id=CVE-2026-91129)
**Home Assistant: mDNS Server-Side Request Forgery**
![](https://img.shields.io/static/v1?label=Vendor&message=home-assistant&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=core&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%202026.2.3&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-918%3A%20Server-Side%20Request%20Forgery%20%28SSRF%29&color=brightgreen)
### Description
Home Assistant is open source home automation software focused on local control and privacy. Prior to 2026.2.3, the IPP integration automatically processed unauthenticated _ipp._tcp.local mDNS announcements in homeassistant/components/ipp/config_flow.py, where async_step_zeroconf passed attacker-controlled host, port, and base_path values to validate_input for printer metadata retrieval. Because the shared HTTP client followed attacker-controlled cross-origin redirects without blocking loopback targets, a local-network attacker could redirect the request to 127.0.0.1 or another internal service without user interaction or prior IPP configuration. This issue is fixed in version 2026.2.3.
### POC
#### Reference
- https://github.com/advisories/GHSA-4ghv-53cq-7wp3
#### Github
No PoCs found on GitHub currently.
+18
View File
@@ -0,0 +1,18 @@
### [CVE-2026-91130](https://www.cve.org/CVERecord?id=CVE-2026-91130)
**Home Assistant: XSS in Statistics Graph Card**
![](https://img.shields.io/static/v1?label=Vendor&message=home-assistant&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=core&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3C%202026.7.0&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-80%3A%20Improper%20Neutralization%20of%20Script-Related%20HTML%20Tags%20in%20a%20Web%20Page%20%28Basic%20XSS%29&color=brightgreen)
### Description
Home Assistant is open source home automation software focused on local control and privacy. Prior to 2026.7.0, the Statistics Graph card in src/components/chart/statistics-chart.ts passed entity names through getStatisticLabel and computeStateName and interpolated param.seriesName into ECharts tooltip HTML without escaping. An authenticated user or an integration that supplies a malicious default entity name could cause script-related HTML to execute when a viewer hovered over a data point. Mean, State, Sum, and Change fields in the default Line chart configuration were affected, while Bar charts were not. This issue is fixed in version 2026.7.0.
### POC
#### Reference
- https://github.com/advisories/GHSA-wx4m-69m9-gx3m
#### Github
No PoCs found on GitHub currently.
+4 -4
View File
@@ -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, 83,294 CVEs with public proof-of-concept exploits">
role="img" aria-label="PoC Index, 83,336 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,13 +19,13 @@
<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">172,592</text>
fill="#e6edf3" letter-spacing="-0.5">172,634</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">83,294</text>
fill="#2f81f7" letter-spacing="-0.5">83,336</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,202</text>
fill="#f85149" letter-spacing="-0.5">1,204</text>
<text x="1010" y="117" font-family="ui-monospace,SFMono-Regular,Menlo,Consolas,monospace" font-size="12"
fill="#6e7681" letter-spacing="1.6">KNOWN EXPLOITED</text>
</svg>

Before

Width:  |  Height:  |  Size: 2.6 KiB

After

Width:  |  Height:  |  Size: 2.6 KiB

+3 -3
View File
@@ -20,13 +20,13 @@
<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">172,592</text>
fill="#e6edf3" letter-spacing="-0.5">172,634</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">83,294</text>
fill="#2f81f7" letter-spacing="-0.5">83,336</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,202</text>
fill="#f85149" letter-spacing="-0.5">1,204</text>
<text x="880" y="459" font-family="ui-monospace,SFMono-Regular,Menlo,Consolas,monospace" font-size="16"
fill="#6e7681" letter-spacing="1.6">KNOWN EXPLOITED</text>

Before

Width:  |  Height:  |  Size: 2.7 KiB

After

Width:  |  Height:  |  Size: 2.7 KiB

+3 -3
View File
@@ -1,5 +1,5 @@
{
"kev": 1202,
"total_cves": 172592,
"with_pocs": 83294
"kev": 1204,
"total_cves": 172634,
"with_pocs": 83336
}
+1 -1
View File
@@ -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-22","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-22","status":"UNAVAILABLE"},"CVE-2010-2782":{"checked":"2026-09-22","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-22","status":"UNAVAILABLE"},"CVE-2011-2553":{"checked":"2026-09-22","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-22","status":"UNAVAILABLE"},"CVE-2012-1304":{"checked":"2026-09-22","status":"UNAVAILABLE"},"CVE-2012-1305":{"checked":"2026-09-22","status":"UNAVAILABLE"},"CVE-2012-1309":{"checked":"2026-09-22","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-22","status":"UNAVAILABLE"},"CVE-2012-3539":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2012-4748":{"checked":"2026-09-22","status":"UNAVAILABLE"},"CVE-2012-4749":{"checked":"2026-09-22","status":"UNAVAILABLE"},"CVE-2012-6315":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2012-6679":{"checked":"2026-09-22","status":"UNAVAILABLE"},"CVE-2013-1298":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-1625":{"checked":"2026-09-22","status":"UNAVAILABLE"},"CVE-2013-1805":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-2649":{"checked":"2026-09-22","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-22","status":"UNAVAILABLE"},"CVE-2014-2923":{"checked":"2026-09-22","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-22","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-22","status":"UNAVAILABLE"},"CVE-2010-2782":{"checked":"2026-09-22","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-22","status":"UNAVAILABLE"},"CVE-2011-2553":{"checked":"2026-09-22","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-22","status":"UNAVAILABLE"},"CVE-2012-1304":{"checked":"2026-09-22","status":"UNAVAILABLE"},"CVE-2012-1305":{"checked":"2026-09-22","status":"UNAVAILABLE"},"CVE-2012-1309":{"checked":"2026-09-22","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-22","status":"UNAVAILABLE"},"CVE-2012-3539":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2012-4748":{"checked":"2026-09-22","status":"UNAVAILABLE"},"CVE-2012-4749":{"checked":"2026-09-22","status":"UNAVAILABLE"},"CVE-2012-6315":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2012-6679":{"checked":"2026-09-22","status":"UNAVAILABLE"},"CVE-2013-1298":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-1625":{"checked":"2026-09-22","status":"UNAVAILABLE"},"CVE-2013-1805":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2013-2649":{"checked":"2026-09-22","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-22","status":"UNAVAILABLE"},"CVE-2014-2923":{"checked":"2026-09-22","status":"UNAVAILABLE"},"CVE-2014-2937":{"checked":"2026-09-01","status":"REJECTED"},"CVE-2Line truncated
+1 -1
View File
@@ -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
View File
@@ -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
View File
@@ -1 +1 @@
{"CVE-2019-0001":{"advisories":[["https://kb.juniper.net/JSA10900",["Vendor Advisory"]],["http://www.securityfocus.com/bid/106541",["Third Party Advisory"]]],"cvss":[["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"],["3.0",7.5,"HIGH","CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","[email protected]","Secondary"],["2.0",7.1,"HIGH","AV:N/AC:M/Au:N/C:N/I:N/A:C","[email protected]","Primary"]]},"CVE-2019-0024":{"advisories":[["https://kb.juniper.net/JSA10918",["Vendor Advisory","Patch"]]],"cvss":[["3.0",5.4,"MEDIUM","CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","[email protected]","Primary"],["3.0",5.4,"MEDIUM","CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","[email protected]","Secondary"],["2.0",3.5,"LOW","AV:N/AC:M/Au:S/C:N/I:P/A:N","[email protected]","Primary"]]},"CVE-2019-0028":{"advisories":[["https://kb.juniper.net/JSA10932",["Vendor Advisory","Mitigation"]],["http://www.securityfocus.com/bid/107892",["Advisory"]]],"cvss":[["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"],["3.0",7.5,"HIGH","CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","[email protected]","Secondary"],["2.0",5.0,"MEDIUM","AV:N/AC:L/Au:N/C:N/I:N/A:P","[email protected]","Primary"]]},"CVE-2019-0053":{"advisories":[["https://kb.juniper.net/JSA10947",["Vendor Advisory"]],["http://packetstormsecurity.com/files/153746/FreeBSD-Security-Advisory-FreeBSD-SA-19-12.telnet.html",["Third Party Advisory"]],["https://lists.debian.org/debian-lts-announce/2022/11/msg00033.html",["Third Party Advisory","Issue Tracking"]],["https://seclists.org/bugtraq/2019/Jul/45",["Third Party Advisory"]],["https://security.FreeBSD.org/advisories/FreeBSD-SA-19:12.telnet.asc",["Third Party Advisory"]],["https://www.exploit-db.com/exploits/45982",["Third Party Advisory","Exploit"]]],"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.0",7.8,"HIGH","CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","[email protected]","Secondary"],["2.0",4.6,"MEDIUM","AV:L/AC:L/Au:N/C:P/I:P/A:P","[email protected]","Primary"]]},"CVE-2019-0090":{"advisories":[["https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00213.html",["Vendor Advisory"]],["https://support.f5.com/csp/article/K59145983",["Third Party Advisory"]]],"cvss":[["3.1",7.1,"HIGH","CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/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-2019-0114":{"advisories":[["https://www.intel.com/content/www/us/en/security-center/advisory/INTEL-SA-00218.html",["Vendor Advisory"]],["http://www.securityfocus.com/bid/108385",["Third Party Advisory"]]],"cvss":[["3.0",4.7,"MEDIUM","CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","[email protected]","Primary"],["2.0",1.9,"LOW","AV:L/AC:M/Au:N/C:N/I:N/A:P","[email protected]","Primary"]]},"CVE-2019-0128":{"advisories":[["https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00224.html",["Vendor Advisory","Patch"]],["http://www.securityfocus.com/bid/108767",["Third Party Advisory"]],["https://support.lenovo.com/us/en/product_security/LEN-27840",["Third Party 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",4.6,"MEDIUM","AV:L/AC:L/Au:N/C:P/I:P/A:P","[email protected]","Primary"]]},"CVE-2019-0129":{"advisories":[["https://www.intel.com/content/www/us/en/security-center/advisory/INTEL-SA-00229.html",["Vendor Advisory"]]],"cvss":[["3.0",7.8,"HIGH","CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"],["2.0",4.6,"MEDIUM","AV:L/AC:L/Au:N/C:P/I:P/A:P","[email protected]","Primary"]]},"CVE-2019-0130":{"advisories":[["https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00226.html",["Vendor Advisory","Patch"]],["http://www.securityfocus.com/bid/108775",["Third Party Advisory"]],["https://support.lenovo.com/us/en/product_security/LEN-27843",["Third Party Advisory"]]],"cvss":[["3.1",7.4,"HIGH","CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:H","[email protected]","Primary"],["2.0",4.3,"MEDIUM","AV:N/AC:M/Au:N/C:N/I:N/A:P","[email protected]","Primary"]]},"CVE-2019-0135":{"advisories":[["https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00231.html",["Vendor Advisory"]],["https://support.lenovo.com/us/en/product_security/LEN-27843",["Third Party 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",4.6,"MEDIUM","AV:L/AC:L/Au:N/C:P/I:P/A:P","[email protected]","Primary"]]},"CVE-2019-0136":{"advisories":[["http://www.securityfocus.com/bid/108777",["Third Party Advisory"]],["https://support.lenovo.com/us/en/product_security/LEN-27828",["Third Party Advisory"]],["https://usn.ubuntu.com/4115-1",["Advisory"]],["https://usn.ubuntu.com/4118-1",["Advisory"]],["https://usn.ubuntu.com/4145-1",["Advisory"]],["https://usn.ubuntu.com/4147-1",["Advisory"]]],"cvss":[["3.0",7.4,"HIGH","CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H","nvLine truncated
{"CVE-2019-0001":{"advisories":[["https://kb.juniper.net/JSA10900",["Vendor Advisory"]],["http://www.securityfocus.com/bid/106541",["Third Party Advisory"]]],"cvss":[["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"],["3.0",7.5,"HIGH","CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","[email protected]","Secondary"],["2.0",7.1,"HIGH","AV:N/AC:M/Au:N/C:N/I:N/A:C","[email protected]","Primary"]]},"CVE-2019-0024":{"advisories":[["https://kb.juniper.net/JSA10918",["Vendor Advisory","Patch"]]],"cvss":[["3.0",5.4,"MEDIUM","CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","[email protected]","Primary"],["3.0",5.4,"MEDIUM","CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","[email protected]","Secondary"],["2.0",3.5,"LOW","AV:N/AC:M/Au:S/C:N/I:P/A:N","[email protected]","Primary"]]},"CVE-2019-0028":{"advisories":[["https://kb.juniper.net/JSA10932",["Vendor Advisory","Mitigation"]],["http://www.securityfocus.com/bid/107892",["Advisory"]]],"cvss":[["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"],["3.0",7.5,"HIGH","CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","[email protected]","Secondary"],["2.0",5.0,"MEDIUM","AV:N/AC:L/Au:N/C:N/I:N/A:P","[email protected]","Primary"]]},"CVE-2019-0053":{"advisories":[["https://kb.juniper.net/JSA10947",["Vendor Advisory"]],["http://packetstormsecurity.com/files/153746/FreeBSD-Security-Advisory-FreeBSD-SA-19-12.telnet.html",["Third Party Advisory"]],["https://lists.debian.org/debian-lts-announce/2022/11/msg00033.html",["Third Party Advisory","Issue Tracking"]],["https://seclists.org/bugtraq/2019/Jul/45",["Third Party Advisory"]],["https://security.FreeBSD.org/advisories/FreeBSD-SA-19:12.telnet.asc",["Third Party Advisory"]],["https://www.exploit-db.com/exploits/45982",["Third Party Advisory","Exploit"]]],"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.0",7.8,"HIGH","CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","[email protected]","Secondary"],["2.0",4.6,"MEDIUM","AV:L/AC:L/Au:N/C:P/I:P/A:P","[email protected]","Primary"]]},"CVE-2019-0090":{"advisories":[["https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00213.html",["Vendor Advisory"]],["https://support.f5.com/csp/article/K59145983",["Third Party Advisory"]]],"cvss":[["3.1",7.1,"HIGH","CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/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-2019-0114":{"advisories":[["https://www.intel.com/content/www/us/en/security-center/advisory/INTEL-SA-00218.html",["Vendor Advisory"]],["http://www.securityfocus.com/bid/108385",["Third Party Advisory"]]],"cvss":[["3.0",4.7,"MEDIUM","CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","[email protected]","Primary"],["2.0",1.9,"LOW","AV:L/AC:M/Au:N/C:N/I:N/A:P","[email protected]","Primary"]]},"CVE-2019-0128":{"advisories":[["https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00224.html",["Vendor Advisory","Patch"]],["http://www.securityfocus.com/bid/108767",["Third Party Advisory"]],["https://support.lenovo.com/us/en/product_security/LEN-27840",["Third Party 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",4.6,"MEDIUM","AV:L/AC:L/Au:N/C:P/I:P/A:P","[email protected]","Primary"]]},"CVE-2019-0129":{"advisories":[["https://www.intel.com/content/www/us/en/security-center/advisory/INTEL-SA-00229.html",["Vendor Advisory"]]],"cvss":[["3.0",7.8,"HIGH","CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"],["2.0",4.6,"MEDIUM","AV:L/AC:L/Au:N/C:P/I:P/A:P","[email protected]","Primary"]]},"CVE-2019-0130":{"advisories":[["https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00226.html",["Vendor Advisory","Patch"]],["http://www.securityfocus.com/bid/108775",["Third Party Advisory"]],["https://support.lenovo.com/us/en/product_security/LEN-27843",["Third Party Advisory"]]],"cvss":[["3.1",7.4,"HIGH","CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:H","[email protected]","Primary"],["2.0",4.3,"MEDIUM","AV:N/AC:M/Au:N/C:N/I:N/A:P","[email protected]","Primary"]]},"CVE-2019-0135":{"advisories":[["https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00231.html",["Vendor Advisory"]],["https://support.lenovo.com/us/en/product_security/LEN-27843",["Third Party 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",4.6,"MEDIUM","AV:L/AC:L/Au:N/C:P/I:P/A:P","[email protected]","Primary"]]},"CVE-2019-0136":{"advisories":[["http://www.securityfocus.com/bid/108777",["Third Party Advisory"]],["https://support.lenovo.com/us/en/product_security/LEN-27828",["Third Party Advisory"]],["https://usn.ubuntu.com/4115-1",["Advisory"]],["https://usn.ubuntu.com/4118-1",["Advisory"]],["https://usn.ubuntu.com/4145-1",["Advisory"]],["https://usn.ubuntu.com/4147-1",["Advisory"]]],"cvss":[["3.0",7.4,"HIGH","CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H","nvLine truncated
+1 -1
View File
@@ -1 +1 @@
{"CVE-2023-0001":{"advisories":[["https://security.paloaltonetworks.com/CVE-2023-0001",["Vendor Advisory"]]],"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"],["3.1",6.0,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:H","[email protected]","Secondary"]]},"CVE-2023-0002":{"advisories":[["https://security.paloaltonetworks.com/CVE-2023-0002",["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",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-2023-0003":{"advisories":[["https://security.paloaltonetworks.com/CVE-2023-0003",["Vendor Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/3N4NJ7FR4X4FPZUGNTQAPSTVB2HB2Y4A",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/E72T67UPDRXHIDLO3OROR25YAMN4GGW5",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/FNA62Q767CFAFHBCDKYNPBMZWB7TWYVU",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/HMEELCREWMRT6NS7HWXLA6XFLLMO36HE",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/HT7T2R4MQKLIF4ODV4BDLPARWFPCJ5CZ",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/LKYHSZQFDNR7RSA7LHVLLIAQMVYCUGBG",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/UEJWL67XR67JAGEL2ZK22NA3BRKNMZNY",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/VEEQIN5242K5NBE2CZ4DYTNA5B4YTYE5",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/VKFMKD4MJZIKFQJAAJ4VZ2FHIJ764A76",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/X6QXN4ORIVF6XBW4WWFE7VNPVC74S45Y",["Third Party Advisory"]]],"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]","Primary"],["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-2023-0004":{"advisories":[["https://security.paloaltonetworks.com/CVE-2023-0004",["Vendor Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/3N4NJ7FR4X4FPZUGNTQAPSTVB2HB2Y4A",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/E72T67UPDRXHIDLO3OROR25YAMN4GGW5",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/FNA62Q767CFAFHBCDKYNPBMZWB7TWYVU",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/HT7T2R4MQKLIF4ODV4BDLPARWFPCJ5CZ",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/LKYHSZQFDNR7RSA7LHVLLIAQMVYCUGBG",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/X6QXN4ORIVF6XBW4WWFE7VNPVC74S45Y",["Third Party Advisory"]]],"cvss":[["3.1",6.5,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H","[email protected]","Primary"],["3.1",6.5,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H","[email protected]","Secondary"]]},"CVE-2023-0005":{"advisories":[["https://security.paloaltonetworks.com/CVE-2023-0005",["Vendor Advisory"]]],"cvss":[["3.1",4.9,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","[email protected]","Primary"],["3.1",4.1,"MEDIUM","CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N","[email protected]","Secondary"]]},"CVE-2023-0012":{"advisories":[["https://launchpad.support.sap.com/#/notes/3276120",["Vendor Advisory"]],["https://www.sap.com/documents/2022/02/fa865ea4-167e-0010-bca6-c68f7e60039b.html",["Vendor Advisory"]]],"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"],["3.1",6.4,"MEDIUM","CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H","[email protected]","Secondary"]]},"CVE-2023-0013":{"advisories":[["https://launchpad.support.sap.com/#/notes/3283283",["Vendor Advisory"]],["https://www.sap.com/documents/2022/02/fa865ea4-167e-0010-bca6-c68f7e60039b.html",["Vendor Advisory"]]],"cvss":[["3.1",6.1,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","[email protected]","Primary"],["3.1",6.1,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","[email protected]","Secondary"]]},"CVE-2023-0014":{"advisories":[["https://launchpad.support.sap.com/#/notesLine truncated
{"CVE-2023-0001":{"advisories":[["https://security.paloaltonetworks.com/CVE-2023-0001",["Vendor Advisory"]]],"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"],["3.1",6.0,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:H","[email protected]","Secondary"]]},"CVE-2023-0002":{"advisories":[["https://security.paloaltonetworks.com/CVE-2023-0002",["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",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-2023-0003":{"advisories":[["https://security.paloaltonetworks.com/CVE-2023-0003",["Vendor Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/3N4NJ7FR4X4FPZUGNTQAPSTVB2HB2Y4A",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/E72T67UPDRXHIDLO3OROR25YAMN4GGW5",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/FNA62Q767CFAFHBCDKYNPBMZWB7TWYVU",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/HMEELCREWMRT6NS7HWXLA6XFLLMO36HE",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/HT7T2R4MQKLIF4ODV4BDLPARWFPCJ5CZ",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/LKYHSZQFDNR7RSA7LHVLLIAQMVYCUGBG",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/UEJWL67XR67JAGEL2ZK22NA3BRKNMZNY",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/VEEQIN5242K5NBE2CZ4DYTNA5B4YTYE5",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/VKFMKD4MJZIKFQJAAJ4VZ2FHIJ764A76",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/X6QXN4ORIVF6XBW4WWFE7VNPVC74S45Y",["Third Party Advisory"]]],"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]","Primary"],["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-2023-0004":{"advisories":[["https://security.paloaltonetworks.com/CVE-2023-0004",["Vendor Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/3N4NJ7FR4X4FPZUGNTQAPSTVB2HB2Y4A",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/E72T67UPDRXHIDLO3OROR25YAMN4GGW5",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/FNA62Q767CFAFHBCDKYNPBMZWB7TWYVU",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/HT7T2R4MQKLIF4ODV4BDLPARWFPCJ5CZ",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/LKYHSZQFDNR7RSA7LHVLLIAQMVYCUGBG",["Third Party Advisory"]],["https://lists.fedoraproject.org/archives/list/[email protected]/message/X6QXN4ORIVF6XBW4WWFE7VNPVC74S45Y",["Third Party Advisory"]]],"cvss":[["3.1",6.5,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H","[email protected]","Primary"],["3.1",6.5,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H","[email protected]","Secondary"]]},"CVE-2023-0005":{"advisories":[["https://security.paloaltonetworks.com/CVE-2023-0005",["Vendor Advisory"]]],"cvss":[["3.1",4.9,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","[email protected]","Primary"],["3.1",4.1,"MEDIUM","CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N","[email protected]","Secondary"]]},"CVE-2023-0012":{"advisories":[["https://launchpad.support.sap.com/#/notes/3276120",["Vendor Advisory"]],["https://www.sap.com/documents/2022/02/fa865ea4-167e-0010-bca6-c68f7e60039b.html",["Vendor Advisory"]]],"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"],["3.1",6.4,"MEDIUM","CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H","[email protected]","Secondary"]]},"CVE-2023-0013":{"advisories":[["https://launchpad.support.sap.com/#/notes/3283283",["Vendor Advisory"]],["https://www.sap.com/documents/2022/02/fa865ea4-167e-0010-bca6-c68f7e60039b.html",["Vendor Advisory"]]],"cvss":[["3.1",6.1,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","[email protected]","Primary"],["3.1",6.1,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","[email protected]","Secondary"]]},"CVE-2023-0014":{"advisories":[["https://launchpad.support.sap.com/#/notesLine truncated
+1 -1
View File
@@ -1 +1 @@
{"CVE-2024-0001":{"advisories":[["https://purestorage.com/security",["Vendor Advisory"]]],"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","[email protected]","Primary"],["3.1",10.0,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","[email protected]","Secondary"]]},"CVE-2024-0002":{"advisories":[["https://purestorage.com/security",["Vendor Advisory"]]],"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","[email protected]","Primary"],["3.1",10.0,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","[email protected]","Secondary"]]},"CVE-2024-0003":{"advisories":[["https://purestorage.com/security",["Vendor Advisory"]]],"cvss":[["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"],["3.1",9.1,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","[email protected]","Secondary"]]},"CVE-2024-0004":{"advisories":[["https://purestorage.com/security",["Vendor Advisory"]]],"cvss":[["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"],["3.1",9.1,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","[email protected]","Secondary"]]},"CVE-2024-0005":{"advisories":[["https://purestorage.com/security",["Vendor Advisory"]]],"cvss":[["3.1",8.8,"HIGH","CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"],["3.1",9.1,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","[email protected]","Secondary"]]},"CVE-2024-0006":{"cvss":[["4.0",5.4,"MEDIUM","CVSS:4.0/AV:A/AC:H/AT:N/PR:H/UI:A/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/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-2024-0010":{"advisories":[["https://security.paloaltonetworks.com/CVE-2024-0010",["Vendor Advisory"]]],"cvss":[["3.1",6.1,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","[email protected]","Primary"],["3.1",4.3,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","[email protected]","Secondary"]]},"CVE-2024-0012":{"advisories":[["https://security.paloaltonetworks.com/CVE-2024-0012",["Vendor Advisory"]],["https://unit42.paloaltonetworks.com/cve-2024-0012-cve-2024-9474",["Vendor Advisory"]],["https://labs.watchtowr.com/pots-and-pans-aka-an-sslvpn-palo-alto-pan-os-cve-2024-0012-and-cve-2024-9474",["Third Party Advisory","Exploit"]]],"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: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: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-2024-0014":{"advisories":[["https://source.android.com/security/bulletin/2024-02-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"],["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-2024-0015":{"advisories":[["https://source.android.com/security/bulletin/2024-01-01",["Vendor Advisory","Patch"]],["https://android.googlesource.com/platform/frameworks/base/+/2ce1b7fd37273ea19fbbb6daeeaa6212357b9a70",["Patch"]]],"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-2024-0016":{"advisories":[["https://source.android.com/security/bulletin/2024-01-01",["Vendor Advisory","Patch"]],["https://android.googlesource.com/platform/packages/modules/Bluetooth/+/1d7ba7c8a205522f384e8d5c7c9f26a421cab5f1",["Patch"]]],"cvss":[["3.1",5.3,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","[email protected]","Primary"],["3.1",6.5,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2024-0017":{"advisories":[["https://source.android.com/security/bulletin/2024-01-01",["Vendor Advisory","Patch"]],["https://android.googlesource.com/platform/packages/apps/Camera2/+/5c4c4b35754eef319dcd69c422f0b1ac0c823f6e",["Patch"]]],"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"],["3.1",5.5,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2024-0023":{"advisories":[["https://source.android.com/security/bulletin/2024-01-01",["Vendor Advisory","Patch"]],["https://android.googlesource.com/platform/frameworks/av/+/30b1b34cfd5abfcfee759e7d13167d368ac6c268",["Patch"]]],"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.4,"HIGH","CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2024-0028":{"advisories":[["https://source.android.com/security/bulletLine truncated
{"CVE-2024-0001":{"advisories":[["https://purestorage.com/security",["Vendor Advisory"]]],"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","[email protected]","Primary"],["3.1",10.0,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","[email protected]","Secondary"]]},"CVE-2024-0002":{"advisories":[["https://purestorage.com/security",["Vendor Advisory"]]],"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","[email protected]","Primary"],["3.1",10.0,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","[email protected]","Secondary"]]},"CVE-2024-0003":{"advisories":[["https://purestorage.com/security",["Vendor Advisory"]]],"cvss":[["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"],["3.1",9.1,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","[email protected]","Secondary"]]},"CVE-2024-0004":{"advisories":[["https://purestorage.com/security",["Vendor Advisory"]]],"cvss":[["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"],["3.1",9.1,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","[email protected]","Secondary"]]},"CVE-2024-0005":{"advisories":[["https://purestorage.com/security",["Vendor Advisory"]]],"cvss":[["3.1",8.8,"HIGH","CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","[email protected]","Primary"],["3.1",9.1,"CRITICAL","CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","[email protected]","Secondary"]]},"CVE-2024-0006":{"cvss":[["4.0",5.4,"MEDIUM","CVSS:4.0/AV:A/AC:H/AT:N/PR:H/UI:A/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/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-2024-0010":{"advisories":[["https://security.paloaltonetworks.com/CVE-2024-0010",["Vendor Advisory"]]],"cvss":[["3.1",6.1,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","[email protected]","Primary"],["3.1",4.3,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","[email protected]","Secondary"]]},"CVE-2024-0012":{"advisories":[["https://security.paloaltonetworks.com/CVE-2024-0012",["Vendor Advisory"]],["https://unit42.paloaltonetworks.com/cve-2024-0012-cve-2024-9474",["Vendor Advisory"]],["https://labs.watchtowr.com/pots-and-pans-aka-an-sslvpn-palo-alto-pan-os-cve-2024-0012-and-cve-2024-9474",["Third Party Advisory","Exploit"]]],"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: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: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-2024-0014":{"advisories":[["https://source.android.com/security/bulletin/2024-02-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"],["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-2024-0015":{"advisories":[["https://source.android.com/security/bulletin/2024-01-01",["Vendor Advisory","Patch"]],["https://android.googlesource.com/platform/frameworks/base/+/2ce1b7fd37273ea19fbbb6daeeaa6212357b9a70",["Patch"]]],"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-2024-0016":{"advisories":[["https://source.android.com/security/bulletin/2024-01-01",["Vendor Advisory","Patch"]],["https://android.googlesource.com/platform/packages/modules/Bluetooth/+/1d7ba7c8a205522f384e8d5c7c9f26a421cab5f1",["Patch"]]],"cvss":[["3.1",5.3,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","[email protected]","Primary"],["3.1",6.5,"MEDIUM","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2024-0017":{"advisories":[["https://source.android.com/security/bulletin/2024-01-01",["Vendor Advisory","Patch"]],["https://android.googlesource.com/platform/packages/apps/Camera2/+/5c4c4b35754eef319dcd69c422f0b1ac0c823f6e",["Patch"]]],"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"],["3.1",5.5,"MEDIUM","CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2024-0023":{"advisories":[["https://source.android.com/security/bulletin/2024-01-01",["Vendor Advisory","Patch"]],["https://android.googlesource.com/platform/frameworks/av/+/30b1b34cfd5abfcfee759e7d13167d368ac6c268",["Patch"]]],"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.4,"HIGH","CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary"]]},"CVE-2024-0028":{"advisories":[["https://source.android.com/security/bulletLine truncated
+1 -1
View File
@@ -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-0412":{"cvss":[["4.0",4.3,"MEDIUM","CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U/V:D/U:Amber","NETGEAR","CVE Program CNA"]]},"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 PartLine truncated
+42
View File
@@ -117497,3 +117497,45 @@ CVE-2026-95928 - https://github.com/recommenders-team/recommenders/issues/2368
CVE-2026-96257 - https://github.com/xiaobor123/vuls-find-VxWorks/tree/main/vul-find-FAST_FAC1203R-copy_msg_element
CVE-2026-96258 - https://github.com/CSDVi/cve/issues/5
CVE-2026-96272 - https://hackmd.io/@leediay/sqli-photo-seach-clipbucketv5
CVE-2026-56682 - https://github.com/advisories/GHSA-32gc-64m7-hj7v
CVE-2026-58268 - https://github.com/advisories/GHSA-pg59-5vwg-4jxq
CVE-2026-58270 - https://github.com/advisories/GHSA-jx63-h26r-8cph
CVE-2026-58271 - https://github.com/advisories/GHSA-274f-6w77-8qm9
CVE-2026-59168 - https://github.com/advisories/GHSA-cqxr-jxr2-85pq
CVE-2026-59991 - https://github.com/advisories/GHSA-8q6g-vjhf-jp8m
CVE-2026-61612 - https://github.com/advisories/GHSA-798p-78g2-v556
CVE-2026-62985 - https://github.com/advisories/GHSA-r3r9-wp5j-pq5g
CVE-2026-62987 - https://github.com/advisories/GHSA-fq95-v8xc-jm3v
CVE-2026-63627 - https://github.com/advisories/GHSA-727h-3vm5-qwq6
CVE-2026-63628 - https://github.com/advisories/GHSA-vc9j-9wph-qghj
CVE-2026-75510 - https://github.com/advisories/GHSA-8gr3-5j6f-25gp
CVE-2026-76909 - https://github.com/advisories/GHSA-7hvx-28gp-mf6j
CVE-2026-76910 - https://github.com/advisories/GHSA-8xcj-9hfr-fh9j
CVE-2026-77243 - https://github.com/advisories/GHSA-3r68-hf9h-887v
CVE-2026-77244 - https://github.com/advisories/GHSA-wrhw-j3f9-8vc6
CVE-2026-77246 - https://github.com/advisories/GHSA-wv8v-v4c5-v75j
CVE-2026-77247 - https://github.com/advisories/GHSA-f6pj-qv47-g96w
CVE-2026-77249 - https://github.com/advisories/GHSA-v9m3-wfh8-5646
CVE-2026-77250 - https://github.com/advisories/GHSA-g5xv-mhgm-v5f6
CVE-2026-77251 - https://github.com/advisories/GHSA-w66g-j6c4-hcfc
CVE-2026-77253 - https://github.com/advisories/GHSA-vc25-24vv-fxxm
CVE-2026-77257 - https://github.com/advisories/GHSA-mrq8-fv7v-hhjg
CVE-2026-77258 - https://github.com/advisories/GHSA-93xw-j965-9mx3
CVE-2026-77261 - https://github.com/advisories/GHSA-6529-c226-h328
CVE-2026-77262 - https://github.com/advisories/GHSA-p6hp-93wp-fh6p
CVE-2026-77266 - https://github.com/advisories/GHSA-mfv2-4wvm-9pgp
CVE-2026-77267 - https://github.com/advisories/GHSA-5wf4-jqxh-8gm3
CVE-2026-77271 - https://github.com/advisories/GHSA-6vmq-24h2-pj7j
CVE-2026-77272 - https://github.com/advisories/GHSA-g2r2-3j32-j27x
CVE-2026-77274 - https://github.com/advisories/GHSA-hgcf-4mq8-5266
CVE-2026-77322 - https://github.com/advisories/GHSA-8h6x-h86x-75wh
CVE-2026-77528 - https://github.com/advisories/GHSA-hxp9-w8x3-p566
CVE-2026-77560 - https://github.com/advisories/GHSA-328g-jx67-v94g
CVE-2026-77561 - https://github.com/advisories/GHSA-9xhm-w3wj-xhqh
CVE-2026-79767 - https://github.com/advisories/GHSA-gfjv-gqf2-c888
CVE-2026-79913 - https://github.com/advisories/GHSA-jvh5-97xg-v99f
CVE-2026-85740 - https://github.com/advisories/GHSA-vv3m-f8x4-7377
CVE-2026-86062 - https://github.com/advisories/GHSA-xpjq-3w4w-w5wr
CVE-2026-88010 - https://github.com/advisories/GHSA-8fcf-v89g-xpg6
CVE-2026-91129 - https://github.com/advisories/GHSA-4ghv-53cq-7wp3
CVE-2026-91130 - https://github.com/advisories/GHSA-wx4m-69m9-gx3m