Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
he primary risk is denial of service (DoS) due to excessive memory or CPU consumption when handling very large requests. The implementation has been updated to align with the HTTP specification, ensuring that `Transfer-Encoding` takes precedence over `Content-Length`. The issue is fixed in Hono v4.9.7, and all users should upgrade immediately. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/honojs/hono/security/advisories/GHSA-92vj-g62v-jqhh - https://github.com/honojs/hono/commit/605c70560b52f13af10379f79b76717042fafe8d
CVE ID: CVE-2025-59140 State: PUBLISHED Published: 2025-09-15T19:09:53.500Z Last Updated: 2025-09-16T13:48:48.092Z Vendors: Qix- Products: node-backslash Problem Types: CWE-506 Description: backlash parses collected strings with escapes. On 8 September 2025, the npm publishing account for backslash was taken over after a phishing attack. Version 0.2.1 was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments. Local environments, server environments, command line applications, etc. are not affected. If the package was used in a browser
nvironments, server environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a direct <script> inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt. The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper. On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised
wner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. Users should upgrade to the latest patch version, completely remove their node_modules directory, clean their package manager's global cache, and rebuild any browser bundles from scratch. Those operating private registries or registry mirrors should purge the offending versions from any caches. This issues is resolved in 0.2.2. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/Qix-/node-backslash/security/advisories/GHSA-53mq-f4w3-f7qv - https://github.com/debug-js/debug/issues/1005 - https://socket.dev/blog/npm-author-qix-
advisories/GHSA-53mq-f4w3-f7qv - https://github.com/debug-js/debug/issues/1005 - https://socket.dev/blog/npm-author-qix-compromised-in-major-supply-chain-attack - https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised - https://www.ox.security/blog/npm-packages-compromised
CVE ID: CVE-2025-59141 State: PUBLISHED Published: 2025-09-15T19:09:58.661Z Last Updated: 2025-09-16T13:47:52.535Z Vendors: Qix- Products: node-simple-swizzle Problem Types: CWE-506 Description: simple-swizzle swizzles function arguments. On 8 September 2025, the npm publishing account for simple-swizzle was taken over after a phishing attack. Version 0.2.3 was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments. Local environments, server environments, command line applications, etc. are not affected. If the package was used in a b
ocal environments, server environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a direct <script> inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt. The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper. On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compr
kage owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. Users should update to the latest patch version, completely remove their node_modules directory, clean their package manager's global cache, and rebuild any browser bundles from scratch. Those operating private registries or registry mirrors should purge the offending versions from any caches. This issue is resolved in 0.2.4. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/Qix-/node-simple-swizzle/security/advisories/GHSA-9g9j-rggx-7fmg - https://github.com/debug-js/debug/issues/1005 - https://socket.dev/blog/npm-au
security/advisories/GHSA-9g9j-rggx-7fmg - https://github.com/debug-js/debug/issues/1005 - https://socket.dev/blog/npm-author-qix-compromised-in-major-supply-chain-attack - https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised - https://www.ox.security/blog/npm-packages-compromised
CVE ID: CVE-2025-59142 State: PUBLISHED Published: 2025-09-15T19:10:07.595Z Last Updated: 2025-09-15T19:45:39.946Z Vendors: Qix- Products: color-string Problem Types: CWE-506 Description: color-string is a parser and generator for CSS color strings. On 8 September 2025, the npm publishing account for color-string was taken over after a phishing attack. Version 2.1.1 was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments. Local environments, server environments, command line applications, etc. are not affected. If the package was us
nments. Local environments, server environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a direct <script> inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt. The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. npm removed the offending package from the registry over the course of the day on 8 September. On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. This issue has
ns to help cache-bust those using private registries who might still have the compromised version cached. This issue has been resolved in 2.1.2. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/Qix-/color-string/security/advisories/GHSA-286p-vc9p-p5qv - https://github.com/debug-js/debug/issues/1005 - https://socket.dev/blog/npm-author-qix-compromised-in-major-supply-chain-attack - https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised - https://www.ox.security/blog/npm-packages-compromised
CVE ID: CVE-2025-59143 State: PUBLISHED Published: 2025-09-15T19:10:01.610Z Last Updated: 2025-09-15T19:50:50.772Z Vendors: Qix- Products: color Problem Types: CWE-506 Description: color is a Javascript color conversion and manipulation library. On 8 September 2025, the npm publishing account for color was taken over after a phishing attack. Version 5.0.1 was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments. Local environments, server environments, command line applications, etc. are not affected. If the package was used in a bro
al environments, server environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a direct <script> inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt. The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper. On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the comprom
ge owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. Users should update to the latest patch version, completely remove their node_modules directory, clean their package manager's global cache, and rebuild any browser bundles from scratch. Those operating private registries or registry mirrors should purge the offending versions from any caches. This issues has been resolved in 5.0.2. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/Qix-/color/security/advisories/GHSA-qrmh-qg46-72pp - https://github.com/debug-js/debug/issues/1005 - https://socket.dev/blog/npm-author-qix-
advisories/GHSA-qrmh-qg46-72pp - https://github.com/debug-js/debug/issues/1005 - https://socket.dev/blog/npm-author-qix-compromised-in-major-supply-chain-attack - https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised - https://www.ox.security/blog/npm-packages-compromised
CVE ID: CVE-2025-59144 State: PUBLISHED Published: 2025-09-15T19:10:04.053Z Last Updated: 2025-09-15T19:46:39.190Z Vendors: debug-js Products: debug Problem Types: CWE-506 Description: debug is a JavaScript debugging utility. On 8 September 2025, the npm publishing account for debug was taken over after a phishing attack. Version 4.4.2 was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments. Local environments, server environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a
ver environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a direct <script> inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt. The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper. On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached.
ew patch versions to help cache-bust those using private registries who might still have the compromised version cached. Users should upgrade to the latest patch version, completely remove their node_modules directory, clean their package manager's global cache, and rebuild any browser bundles from scratch. Those operating private registries or registry mirrors should purge the offending versions from any caches. This issue has been resolved in 4.4.3. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/debug-js/debug/security/advisories/GHSA-4x49-vf9v-38px - https://github.com/debug-js/debug/issues/1005 - https://socket.dev/blog/npm-author-qix-compromised-in-m
4x49-vf9v-38px - https://github.com/debug-js/debug/issues/1005 - https://socket.dev/blog/npm-author-qix-compromised-in-major-supply-chain-attack - https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised - https://www.ox.security/blog/npm-packages-compromised
CVE ID: CVE-2025-59145 State: PUBLISHED Published: 2025-09-15T20:32:43.877Z Last Updated: 2025-09-15T20:39:58.389Z Vendors: colorjs Products: color-name Problem Types: CWE-506 Description: color-name is a JSON with CSS color names. On 8 September 2025, an npm publishing account for color-name was taken over after a phishing attack. Version 2.0.1 was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments. Local environments, server environments, command line applications, etc. are not affected. If the package was used in a browser conte
ments, server environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a direct <script> inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt. The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. See references below for more information on the payload. npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper. On 13 September, the package owner published new patch versions to help cache-bust those using pri
oads from npm proper. On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. Users should update to the latest patch version, completely remove their node_modules directory, clean their package manager's global cache, and rebuild any browser bundles from scratch. Those operating private registries or registry mirrors should purge the offending versions from any caches. This issue is resolved in 2.0.2. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/colorjs/color-name/security/advisories/GHSA-5fvm-p68v-5wmh - https://github.com/debug-js/debug/issu
- https://github.com/colorjs/color-name/security/advisories/GHSA-5fvm-p68v-5wmh - https://github.com/debug-js/debug/issues/1005 - https://socket.dev/blog/npm-author-qix-compromised-in-major-supply-chain-attack - https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised - https://www.ox.security/blog/npm-packages-compromised
CVE ID: CVE-2025-59146 State: PUBLISHED Published: 2025-10-09T18:58:50.893Z Last Updated: 2025-10-09T19:07:40.946Z Severity: HIGH (CVSS 8.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N) Vendors: QuantumNous Products: new-api Problem Types: CWE-918 Description: New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. An authenticated Server-Side Request Forgery (SSRF) vulnerability exists in versions prior to 0.9.0.5. A feature within the application allows authenticated users to submit a URL for the server to process its content. The application fails to properly validate this user-supplied URL before making a server-side request. This vulnerab
nt. The application fails to properly validate this user-supplied URL before making a server-side request. This vulnerability is not limited to image URLs and can be triggered with any link provided to the vulnerable endpoint. Since user registration is often enabled by default, any registered user can exploit this. By crafting a malicious URL, an attacker can coerce the server to send requests to arbitrary internal or external services. The vulnerability has been patched in version 0.9.0.5. The patch introduces a comprehensive, user-configurable SSRF protection module, which is enabled by default to protect server security. This new feature provides administrators with granular control over
ch is enabled by default to protect server security. This new feature provides administrators with granular control over outbound requests made by the server. For users who cannot upgrade immediately, some temporary mitigation options are available. Enable new-api image processing worker (new-api-worker) and/or configure egress firewall rules. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/QuantumNous/new-api/security/advisories/GHSA-xxv6-m6fx-vfhh - https://github.com/QuantumNous/new-api/commit/ef634160986c6f6b087cbfe131074fda862928af
CVE ID: CVE-2025-59147 State: PUBLISHED Published: 2025-10-01T19:27:55.639Z Last Updated: 2025-10-01T19:42:24.032Z Severity: HIGH (CVSS 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) Vendors: OISF Products: suricata Problem Types: CWE-358 Description: Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Versions 7.0.11 and below, as well as 8.0.0, are vulnerable to detection bypass when crafted traffic sends multiple SYN packets with different sequence numbers within the same flow tuple, which can cause Suricata to fail to pick up the TCP session. In IDS mode this can lead to a detection and logging bypass.
ich can cause Suricata to fail to pick up the TCP session. In IDS mode this can lead to a detection and logging bypass. In IPS mode this will lead to the flow getting blocked. This issue is fixed in versions 7.0.12 and 8.0.1. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/OISF/suricata/security/advisories/GHSA-v8hv-6v7x-4c2r - https://github.com/OISF/suricata/commit/be6315dba0d9101b11d16e9dacfe2822b3792f1b - https://github.com/OISF/suricata/commit/e91b03c90385db15e21cf1a0e85b921bf92b039e - https://forum.suricata.io/t/suricata-8-0-1-and-7-0-12-released/6018
CVE ID: CVE-2025-59148 State: PUBLISHED Published: 2025-10-01T19:51:27.388Z Last Updated: 2025-10-01T19:58:13.158Z Severity: HIGH (CVSS 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: OISF Products: suricata Problem Types: CWE-476 Description: Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Versions 8.0.0 and below incorrectly handle the entropy keyword when not anchored to a "sticky" buffer, which can lead to a segmentation fault. This issue is fixed in version 8.0.1. To workaround this issue, users can disable rules using the entropy keyword, or validate they are anchored to a sticky buffer. A
round this issue, users can disable rules using the entropy keyword, or validate they are anchored to a sticky buffer. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/OISF/suricata/security/advisories/GHSA-5qf6-92xg-3rr3 - https://github.com/OISF/suricata/commit/9f32550e18f97ea5d610dd7c36aab0ba142c096c - https://forum.suricata.io/t/suricata-8-0-1-and-7-0-12-released/6018 - https://redmine.openinfosecfoundation.org/issues/7838
CVE ID: CVE-2025-59149 State: PUBLISHED Published: 2025-10-01T20:07:44.042Z Last Updated: 2025-10-01T20:17:41.659Z Severity: MEDIUM (CVSS 6.2 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: OISF Products: suricata Problem Types: CWE-121 Description: Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In version 8.0.0, rules using keyword ldap.responses.attribute_type (which is long) with transforms can lead to a stack buffer overflow during Suricata startup or during a rule reload. This issue is fixed in version 8.0.1. To workaround this issue, users can disable rules with ldap.responses.attribute_type
s issue is fixed in version 8.0.1. To workaround this issue, users can disable rules with ldap.responses.attribute_type and transforms. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/OISF/suricata/security/advisories/GHSA-vxcg-38x4-gj7j - https://github.com/OISF/suricata/commit/38a2cba5c397002047d84645f5ab770ff88020e1 - https://forum.suricata.io/t/suricata-8-0-1-and-7-0-12-released/6018 - https://redmine.openinfosecfoundation.org/issues/7861
CVE ID: CVE-2025-59150 State: PUBLISHED Published: 2025-10-01T20:23:54.207Z Last Updated: 2025-10-23T13:12:27.248Z Severity: HIGH (CVSS 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: OISF Products: suricata Problem Types: CWE-476 Description: Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Version 8.0.0's usage of the tls.subjectaltname keyword can lead to a segmentation fault when the decoded subjectaltname contains a NULL byte. This issue is fixed in version 8.0.1. To workaround this issue, disable rules using the tls.subjectaltname keyword. Additional Analyst Notes: - CISA ADP Vulnrichment:
ound this issue, disable rules using the tls.subjectaltname keyword. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://github.com/OISF/suricata/security/advisories/GHSA-mhv7-qfmj-m3f3 - https://github.com/OISF/suricata/commit/d590fdfe42e995fd558315f0c24f9a352e21479d - https://forum.suricata.io/t/suricata-8-0-1-and-7-0-12-released/6018 - https://redmine.openinfosecfoundation.org/issues/7881
CVE ID: CVE-2025-59151 State: PUBLISHED Published: 2025-10-27T19:42:59.596Z Last Updated: 2025-10-27T20:24:05.879Z Severity: HIGH (CVSS 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L) Vendors: pi-hole Products: web Problem Types: CWE-93, CWE-113 Description: Pi-hole Admin Interface is a web interface for managing Pi-hole, a network-level advertisement and internet tracker blocking application. Pi-hole Admin Interface before 6.3 is vulnerable to Carriage Return Line Feed (CRLF) injection. When a request is made to a file ending with the .lp extension, the application performs a redirect without properly sanitizing the input. An attacker can inject carriage return and line feed characters (%
rms a redirect without properly sanitizing the input. An attacker can inject carriage return and line feed characters (%0d%0a) to manipulate both the headers and the content of the HTTP response. This enables the injection of arbitrary HTTP response headers, potentially leading to session fixation, cache poisoning, and the weakening or bypassing of browser-based security mechanisms such as Content Security Policy or X-XSS-Protection. This vulnerability is fixed in 6.3. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/pi-hole/web/security/advisories/GHSA-5v79-p56f-x7c4
CVE ID: CVE-2025-59152 State: PUBLISHED Published: 2025-10-06T15:23:12.526Z Last Updated: 2025-10-06T15:35:41.813Z Severity: HIGH (CVSS 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: litestar-org Products: litestar Problem Types: CWE-807 Description: Litestar is an Asynchronous Server Gateway Interface (ASGI) framework. In version 2.17.0, rate limits can be completely bypassed by manipulating the X-Forwarded-For header. This renders IP-based rate limiting ineffective against determined attackers. Litestar's RateLimitMiddleware uses `cache_key_from_request()` to generate cache keys for rate limiting. When an X-Forwarded-For header is present, the middleware trusts it unconditional
generate cache keys for rate limiting. When an X-Forwarded-For header is present, the middleware trusts it unconditionally and uses its value as part of the client identifier. Since clients can set arbitrary X-Forwarded-For values, each different spoofed IP creates a separate rate limit bucket. An attacker can rotate through different header values to avoid hitting any single bucket's limit. This affects any Litestar application using RateLimitMiddleware with default settings, which likely includes most applications that implement rate limiting. Version 2.18.0 contains a patch for the vulnerability. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/litestar-
tch for the vulnerability. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/litestar-org/litestar/security/advisories/GHSA-hm36-ffrh-c77c - https://github.com/litestar-org/litestar/commit/42a89e043e50b515f8548a93954fe143f63cf9fb - https://github.com/litestar-org/litestar/blob/26f20ac6c52de2b4bf81161f7560c8bb4af6f382/litestar/middleware/rate_limit.py#L127