GitPython's Submodule.move() API does not properly validate intermediate symbolic links in the destination path, allowing an attacker-controlled repository to redirect submodule moves outside the parent repository worktree. This can cause the submodule checkout to be moved to an attacker-chosen directory outside the intended location, corrupting the parent repository's index and configuration. The vulnerability affects GitPython versions from 0.26.0 up to but not including 0.33.0. No code execution or confidentiality impact has been demonstrated. A fix is available in version 0.33.0.
pypdf versions prior to 6.21.3 contain a vulnerability where opening a crafted PDF with cross-reference streams declaring very large entry counts can cause excessive memory consumption. This is due to the way highly compressible streams, /Prev chains, and negative /Index counts multiply the number of parsed entries, bypassing existing limits. The issue is fixed in version 6.21.3.
Nuxt is an open-source web development framework for Vue.js. From 3.0.0 until 4.6.3, the Nuxt development server can expose the Nitro 2 development bundle at <buildDir>/dev/index.mjs through Vite file serving when the server is reachable over HTTP. Nitro inlines private runtimeConfig values resolved at build time into that bundle, including secrets configured in nuxt.config, and Nuxt 4.6.0 and later also inline the generated development appSecret. The default localhost binding limits remote exposure, production builds and Nitro 3 are not affected, and runtime configuration supplied only through NUXT_* environment variables at server startup is not inlined. This issue is fixed in version 4.6.3.
Node minimatch versions prior to 11.0.1 contain a vulnerability in the firstPhasePreProcess() function that allows a crafted glob pattern with repeated **/.. segments to cause excessive CPU and memory usage during pattern compilation. This can lead to denial of service conditions. The issue is resolved in version 11.0.1.
CVE-2026-119131 is a denial of service vulnerability in wasmtime versions 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3. It occurs in the wasmtime-wasi-http component when guests send long request URLs with a '?' character after byte 65535, causing an integer overflow in a u16 index. This overflow triggers a host panic, crashing the host process.
An OS command injection vulnerability exists in the 'open' software versions 7.2.0 up to but not including 11.0.0, 2.0.0 up to 2.12.0, and 1.0.137 up to 1.18.33. This flaw allows attackers to execute arbitrary PowerShell code on Windows and Windows Subsystem for Linux (WSL) by supplying crafted URLs containing $(...) subexpressions. The vulnerability arises because these subexpressions are passed unescaped to the powershell -EncodedCommand in index.js, enabling code execution.
A vulnerability in virtualenv prior to version 21.14.9 allows pip seeding with the --download option to bypass wheel digest verification when using the default PyPI index. This occurs because the verification path is skipped, potentially allowing selection of a wheel matching the package and version without verifying its SHA-256 digest against PyPI metadata. The issue does not affect TLS security or allow control over the index response. It is fixed in version 21.14.9.
A vulnerability in the Linux kernel's SCSI libiscsi component allows a target to specify an invalid task index in management responses, leading to a NULL pointer dereference and kernel crash. The flaw occurs because the task index is only bounds-checked against the maximum command slots but not verified to be in flight or valid, causing dereferencing of a NULL connection pointer. This can be triggered by sending a single unsolicited NOP-In or a Text Response with the same invalid task identifier. The issue has been resolved by requiring the task to be in flight and not a SCSI command, preventing invalid task references.
A vulnerability in the Linux kernel's x86 instruction evaluation code caused by a variable shadowing issue in get_seg_reg_override_idx() leads to incorrect handling of segment register overrides. This results in the function always returning a default segment register value, ignoring FS and GS overrides, and causing an infinite loop when a CS override is present. The flaw can cause the kernel to spin indefinitely, preventing user space from regaining control and leaving CPUs tied up until reboot. Additionally, FS or GS prefix usage can cause emulated results to be written to incorrect memory addresses.
A vulnerability in the Linux kernel's ring-buffer implementation was fixed to correct an off-by-one error in the sub-buffer array base calculation within rb_meta_subbuf_idx(). This flaw caused an index to be one sub-buffer too high, leading to improper initialization of sub-buffer IDs and potential dereferencing of a NULL pointer when userspace maps trace_pipe_raw. The issue affected multiple specific Linux kernel versions and could cause trace data from the previous boot to be discarded on the next boot.
CVE-2026-99154 is a critical vulnerability in the Linux kernel's libiscsi SCSI subsystem. It involves improper handling of a negative task index in the parse_pdu_itt function, allowing out-of-bounds array access. This flaw was fixed by adding lower bound checks on the index to prevent reading before the array. The vulnerability affects Linux kernel version 2.6.33.
CVE-2026-113714 is a vulnerability in virtualenv's wheel download and caching mechanism where downloaded wheel files are placed directly into a reusable cache before verification. The verification process relies on pip's textual output to select the file to verify, which can be manipulated by a malicious package index. This can result in a modified wheel being cached and reused despite failing verification, potentially leading to the use of tampered packages in new environments.