The @hapi/content library, used by the hapi Node.js framework and by @hapi/pez for multipart/form-data parsing, has a flaw in Content.disposition(). A Content-Disposition header with a long parameter token that has no equals sign causes quadratic processing that can block the Node.js event loop. An unauthenticated remote attacker can stall a single-instance service with one crafted multipart request, and applications that pass untrusted headers directly to Content.disposition() are also affected.
hapi project · @hapi/content
Research and translation in progress – available shortly.
Nuxt renders pages after resolving literal or percent-encoded dot segments, while server middleware, Nitro routing and route rules evaluate the unresolved path. A crafted request such as /%2e/admin can therefore render a protected page while path-keyed checks, redirects and per-route security headers are skipped. The issue affects Nuxt 4.6.0 up to 4.6.2 and requires a client that sends dot segments without browser normalisation.
Nuxt · Nuxt
Research and translation in progress – available shortly.
Research and translation in progress – available shortly.
The containerized OpenShift installer downloads inventory and dynamic scripts from remote URLs and runs them without verifying their integrity. An attacker with a Man-in-the-Middle position on the network, or control of the script server, can substitute a malicious executable. It then runs with the installer's user ID and full cluster-provisioning privileges, which allows arbitrary code execution. The risk only applies where INVENTORY_URL or DYNAMIC_SCRIPT_URL is used.
Red Hat · openshift-ansible
IDrive Backup for Windows up to and including version 7.0.1.1 contains a vulnerability in the id_service.exe component that allows a local attacker to execute arbitrary code. An attack requires a local user account on the affected Windows system; the network is not exposed. The issue is fixed in version 7.0.1.2. The CVSS score and CWE classification are provisional because NVD analysis is still pending.
IDrive · IDrive Backup for Windows
IDrive Backup for Windows version 7.0.1.1 and below contains a flaw in the id_service.exe component that allows a local attacker to execute arbitrary code. According to the researcher's write-up, insecure serialization and deserialization of data sent to the local service allows injected code to run with SYSTEM privileges. The attacker needs a logon with low privileges on the affected system; the service is not reachable from remote systems. Version 7.0.1.2 fixes the issue.
IDrive · Backup for Windows
pyasn1, a generic ASN.1 library for Python, decodes binary REAL values with a mantissa-building routine whose run time grows quadratically with the mantissa length. An attacker who can supply ASN.1 data to an application using pyasn1 can send a comparatively small REAL value that keeps a decoding process busy on one CPU core for seconds or longer. The attack works with BER, CER and DER decoding, with or without a schema, and leads to loss of availability.
pyasn1 · pyasn1
pyasn1, a generic ASN.1 library for Python, consumes CPU quadratically when decoding constructed BIT STRING values with many fragments. An attacker who can supply crafted BER, CER or definite-length DER input can stall the decoding process. The flaw causes denial of service only, with no confidentiality or integrity impact, and applies only where an application parses untrusted ASN.1 data with pyasn1.
pyasn1 · pyasn1
pyasn1, a generic ASN.1 library for Python, has a quadratic-time flaw when decoding constructed string types and indefinite-length ANY values in BER and CER data. An attacker who can supply such data to an application that decodes it can send many fragments, which exhausts CPU on the decoding workers. The issue causes denial of service only, with no confidentiality or integrity impact. Exposure depends on whether an application decodes untrusted ASN.1 input, and pyasn1 is often used as a transitive dependency.
pyasn1 · pyasn1
pyasn1 is a generic ASN.1 Python library. Versions from 0.3.3 up to 0.6.5 store the TagSet of every decoded component in a growing set during schemaless container decoding, which causes quadratic CPU work when attacker-supplied BER, CER or DER input contains many long tag IDs with colliding hashes. An unauthenticated remote attacker can send repeated crafted inputs to exhaust decoder CPU and reduce service availability.
pyasn1 · pyasn1
Research and translation in progress – available shortly.
Forge (node-forge) is a JavaScript implementation of TLS and cryptographic functions. Crafted DER or PEM input with deeply nested BIT STRINGs makes asn1.fromDer() consume excessive CPU time and memory, because the maxDepth limit was not applied to BIT STRING contents. A remote, unauthenticated attacker can exhaust resources and crash a Node.js process, so the impact is limited to availability. This is an incomplete fix of CVE-2025-66031.
Digitalbazaar · Forge (node-forge)
node-forge (Forge) versions before 1.4.1 accept a certificate as a CA when it contains a forged extension under the deprecated OIDs 2.5.29.10 or 2.5.29.13, placed before the genuine basicConstraints extension. An attacker who holds a certificate from a CA trusted by the application, where that CA copies extensions from certificate signing requests, can issue certificates for arbitrary names and impersonate servers or clients. Exploitation is complex and depends on such a trusted CA, and a public proof of concept exists.
Digital Bazaar · node-forge
Research and translation in progress – available shortly.
Forge (node-forge) is a JavaScript implementation of TLS. A remote, unauthenticated peer can send a TLS record of another content type in the middle of a fragmented handshake message, which causes an uncaught TypeError in process(). This terminates the affected connection or the Node.js process hosting it, so the impact is limited to availability (CVSS 7.5, A:H). Exposure is highest for Node.js services that use forge's TLS code and accept connections from untrusted peers.
Digital Bazaar · Forge (node-forge)
Forge (node-forge) is a JavaScript implementation of TLS. Before version 1.4.1, the TLS record processing in forge.tls.createConnection() handled each received record recursively, so a single input chunk with thousands of small records (for example heartbeat records) exhausts the JavaScript call stack. The attack needs no authentication and can be started by any peer that connects to a forge TLS server or to a server a forge TLS client connects to. In Node.js applications that call process() from a socket data handler, the uncaught exception terminates the process and drops the connections it serves.
Digital Bazaar · Forge (node-forge)
Research and translation in progress – available shortly.
A heap-based buffer overflow in the vtkWindBladeReader component of VTK 9.6.1 can be triggered by a specially crafted WindBlade .wind data set. A signed byteCount value in the binary data file can produce a zero-sized buffer, and out-of-bounds reads then follow. An attacker who can supply such a file to a vulnerable application can cause a deterministic denial of service and may expose heap-resident data.
Kitware · VTK
A out-of-bounds read vulnerability in the vtkChacoReader InputGraph2 function of VTK 9.6.1 allows an attacker to read memory outside the intended buffer. The flaw is caused by missing validation of neighbor vertex IDs in Chaco graph files, which are later used as point indices. An attacker can trigger it by supplying a specially crafted Chaco file to an application that parses such input, which may lead to a crash or limited information disclosure.
Kitware · VTK
The vtkBMPReader component of the VTK (Visualization Toolkit) library, version 9.6.1 according to the CNA, contains a memory corruption flaw when parsing BMP files with an unsupported bit depth. A specially crafted BMP file can cause a heap-buffer-overflow write, which can crash the application that opens the file. The attack requires that an application using VTK opens a malicious file, which is why exposure mainly concerns upload features or image-processing pipelines.
Kitware · VTK
A memory corruption flaw (out-of-bounds write) in the vtkDEMReader ReadProfiles function of VTK 9.6.1 causes a heap buffer overflow when a specially crafted USGS DEM file is parsed. An attacker who can supply such a file to an application that uses VTK can trigger the flaw, which the advisory describes as an availability impact (crash or denial of service). No authentication is required, but the malicious file must reach the parser. Code execution has not been confirmed.
Kitware · VTK
Research and translation in progress – available shortly.
The PNG reader (vtkPNGReader::vtkPNGReaderUpdate2) of the Visualization Toolkit (VTK) 9.6 contains an invalid pointer dereference. A specially crafted PNG file can crash the process, causing a denial of service. An attacker only needs to supply the malicious file to the application, without authentication or user interaction, if the application accepts untrusted PNG files.
Kitware · VTK
