Vulnerability database
Every flaw the U.S. government’s cybersecurity agency (CISA) has confirmed attackers are using, plus the new WordPress plugin and theme bugs published each day, sorted by what they mean for a small business. We refresh it twice a day. If you see something your website or office runs, tell us.
117 results · page 1 of 3
Sep 21, 2026mport is the MidnightBSD Package Manager.CVE-2026-54584 · Other software · MidnightBSD · reported by GitHubMedium 5.3
mport is the MidnightBSD Package Manager. mport before 2.7.8 used TMPDIR while extracting package metafiles, including when running as root or in setuid/setgid contexts. An attacker able to control the environment for a privileged mport invocation could redirect temporary metadata extraction to an attacker-controlled location. PR 123 ignores unsafe TMPDIR values in privileged contexts and rejects empty TMPDIR. This issue has been patched in version 2.7.8.
- Product
- mport
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Sep 17, 2026mport is the MidnightBSD Package Manager.CVE-2026-54587 · Other software · MidnightBSD · reported by GitHubMedium 5.8
mport is the MidnightBSD Package Manager. Prior to 2.7.8, directory assets handled as ASSET_DIR or ASSET_DIR_OWNER_MODE in libmport/bundle_read_install_pkg.c used path-based mport_mkdirp(), ownership, and permission operations. A local attacker able to modify part of the target installation tree could use dot-dot traversal or substitute symlinks during privileged package installation, causing directory creation or attribute changes to affect attacker-selected paths outside the intended package directories. This issue is fixed in version 2.7.8.
- Product
- mport
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Sep 17, 2026mport is the MidnightBSD Package Manager.CVE-2026-54586 · Other software · MidnightBSD · reported by GitHubMedium 6
mport is the MidnightBSD Package Manager. Prior to 2.7.8, the mport_fetch_index(), mport_fetch_bootstrap_index(), and mport_fetch_bundle() paths in libmport/fetch.c accepted non-HTTPS repository and package mirror URLs without a url_is_https() enforcement check. When a cleartext URL was configured or returned by mirror data, a network-positioned attacker could tamper with package index or package download traffic and compromise package selection or integrity. This issue is fixed in version 2.7.8.
- Product
- mport
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Sep 17, 2026mport is the MidnightBSD Package Manager.CVE-2026-54585 · Other software · MidnightBSD · reported by GitHubMedium 6
mport is the MidnightBSD Package Manager. Prior to 2.7.8, create_sample_file() in libmport/bundle_read_install_pkg.c did not constrain absolute source and destination paths from the sample-file manifest directive to mport->root. A malicious or malformed package manifest could therefore direct privileged sample-file handling to copy or write outside the configured installation root, compromising local filesystem integrity. This issue is fixed in version 2.7.8.
- Product
- mport
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Sep 17, 2026mport is the MidnightBSD Package Manager.CVE-2026-54583 · Other software · MidnightBSD · reported by GitHubHigh 8.3
mport is the MidnightBSD Package Manager. Prior to 2.7.8, libmport/fetch.c did not consistently reject empty, dot, dot-dot, or slash-containing bundle filenames before composing package download and write paths. Malicious package index data could place an unsafe value in indexEntry->bundlefile, and the missing is_valid_bundle_filename() checks allowed downloaded package data to be written outside the intended cache location or to an unsafe destination name. This issue is fixed in version 2.7.8.
- Product
- mport
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Sep 17, 2026mport is the MidnightBSD Package Manager.CVE-2026-54582 · Other software · MidnightBSD · reported by GitHubMedium 6
mport is the MidnightBSD Package Manager. Prior to 2.7.8, package installation lacked a preflight check for incoming non-directory assets that already existed on disk. The affected logic across libmport/check_preconditions.c, libmport/install_primative.c, and libmport/mport_private.h did not apply MPORT_PRECHECK_FILE_CONFLICTS, so a crafted or conflicting package could overwrite a file owned by another package or unmanaged by mport. The check is bypassed only when the operator explicitly enables mport->force. Privileged installation without that override could compromise local filesystem integrity and package database consistency. This issue is fixed in version 2.7.8.
- Product
- mport
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Sep 17, 2026mport is the MidnightBSD Package Manager.CVE-2026-54581 · Other software · MidnightBSD · reported by GitHubHigh 8.3
mport is the MidnightBSD Package Manager. Prior to 2.7.8, the mport_fetch_bootstrap_index() function in libmport/fetch.c could return success when bootstrap index hash verification encountered a missing or invalid hash because the failure path did not preserve a fatal result. A network attacker or compromised mirror able to alter bootstrap index content or its transport path could therefore cause mport to proceed with an unverified or tampered bootstrap package index. This issue is fixed in version 2.7.8.
- Product
- mport
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Sep 17, 2026mport is the MidnightBSD Package Manager.CVE-2026-54580 · Other software · MidnightBSD · reported by GitHubHigh 8.3
mport is the MidnightBSD Package Manager. Prior to 2.7.8, libmport/util.c did not make every truncated, corrupt, or failed zstd stream fatal in mport_decompress_zstd(), and libmport/fetch.c did not consistently propagate those failures to index-fetch callers. A malicious or faulty mirror could supply compressed package index data that caused ZSTD_decompressStream() or an output write to fail while leaving partial index output available for later use, resulting in package-index integrity loss or denial of service. This issue is fixed in version 2.7.8.
- Product
- mport
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Sep 17, 2026mport is the MidnightBSD Package Manager.CVE-2026-54579 · Other software · MidnightBSD · reported by GitHubLow 2.3
mport is the MidnightBSD Package Manager. Prior to 2.7.8, ping() in libmport/ping.c accepted ICMP replies without validating icmp_id or icmp_seq and parsed the reply using a fixed IP-header offset instead of ip_hl. A network attacker able to inject or spoof visible ICMP replies could influence mirror latency selection, while a malformed packet carrying IP options could shift the ICMP header and trigger an out-of-bounds read. This issue is fixed in version 2.7.8.
- Product
- mport
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Sep 17, 2026mport is the MidnightBSD Package Manager.CVE-2026-54578 · Other software · MidnightBSD · reported by GitHubLow 2
mport is the MidnightBSD Package Manager. Prior to 2.7.8, mport_verify_package() in libmport/verify.c could continue after MD5File() or SHA256_File() failed and compare an expected checksum with stale data in the hash buffer rather than a newly computed digest. An attacker able to influence an installed file or the conditions that make hashing fail could receive a misleading integrity result or hide a checksum failure. This issue is fixed in version 2.7.8.
- Product
- mport
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Sep 17, 2026mport is the MidnightBSD Package Manager.CVE-2026-54577 · Other software · MidnightBSD · reported by GitHubLow 2
mport is the MidnightBSD Package Manager. Prior to 2.7.8, the audit command in mport/mport.c computed option-adjusted local_argv and local_argc values but passed the original argument entry to audit_package(). When an operator or automation used an option such as -r before a package name, stale optind state and the unadjusted argument could cause mport to audit the option token instead of the requested package, producing a false-negative or useless result that could leave a vulnerable package unidentified. The corrected parsing resets optind and optreset before using the adjusted local arguments. This issue is fixed in version 2.7.8.
- Product
- mport
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Sep 17, 2026mport is the MidnightBSD Package Manager.CVE-2026-54576 · Other software · MidnightBSD · reported by GitHubMedium 5.8
mport is the MidnightBSD Package Manager. Prior to 2.7.8, do_actual_install() in libmport/bundle_read_install_pkg.c used path-based lstat(), chown(), stat(), and chmod() operations while installing package files. A local attacker with write access to a target directory could replace a checked file with a symlink before privileged ownership or mode changes were applied, redirecting those changes to an attacker-selected path and compromising filesystem integrity or permissions. This issue is fixed in version 2.7.8.
- Product
- mport
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Sep 17, 2026mport is the MidnightBSD Package Manager.CVE-2026-54575 · Other software · MidnightBSD · reported by GitHubMedium 5.8
mport is the MidnightBSD Package Manager. Prior to 2.7.8, privileged package fetch and cache-cleaning operations used race-prone path handling across libmport/fetch.c, libmport/clean.c, libmport/util.c, libmport/bundle_read_install_pkg.c, libmport/delete_primative.c, and libexec/mport.create/mport.create.c. A local attacker with write access to a participating package cache or staging path could race path checks and replacement operations to redirect package downloads, cleanup, or install-related side effects outside the intended cache. The affected lifecycle helper paths also used shell-form invocation, increasing command-line interpretation risk during privileged helper execution. This issue is fixed in version 2.7.8.
- Product
- mport
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Aug 31, 2026pnpm is a package manager.CVE-2026-82393 · Other software · pnpm · reported by GitHubHigh 7.5
pnpm is a package manager. Prior to 10.34.5 and 11.11.0, pnpm accepts a scoped path traversal in a tarball dependency's package.json manifest name because pnpm11/resolving/npm-resolver/src/pickPackage.ts rejects slash characters only for unscoped names. During pnpm install, the unvalidated name reaches raw path joins in pnpm11/installing/deps-resolver/src/resolvePeers.ts, pnpm11/installing/deps-resolver/src/index.ts, and pnpm11/deps/graph-builder/src/lockfileToDepGraph.ts, causing package extraction outside node_modules and allowing attacker-controlled files to overwrite arbitrary filesystem paths even when --ignore-scripts is used. The overwrite can replace shell startup files, Git hooks, or installed package code and lead to code execution. This issue is fixed in versions 10.34.5, and 11.11.0.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Aug 31, 2026pnpm is a package manager.CVE-2026-82392 · Other software · pnpm · reported by GitHubHigh 7.1
pnpm is a package manager. Prior to 10.34.5 and from 11.0.0 until 11.11.0, pnpm parses the package name from attacker-controlled pnpm-lock.yaml packages keys with dp.parse(depPath).name and uses it without validation in deps/graph-builder/src/lockfileToDepGraph.ts and pnpm11/deps/graph-builder/src/lockfileToDepGraph.ts. The name reaches path.join(modules, pkgName), storeController.importPackage, and pnpm11/lockfile/to-pnp/src/index.ts, allowing package contents to be written outside node_modules when a user runs pnpm install. When dangerouslyAllowAllBuilds or a matching allowBuilds entry permits lifecycle scripts, the escaped package can execute code with the user's privileges. This issue is fixed in versions 10.34.5 and 11.11.0.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Aug 28, 2026A flaw was found in libsolv, a dependency-resolution library used by RPM-based package managers such as dnf and zypper to work with .solv repository cache filesCVE-2026-82327 · Other software · Red Hat · reported by Red HatMedium 5.5
A flaw was found in libsolv, a dependency-resolution library used by RPM-based package managers such as dnf and zypper to work with .solv repository cache files. When libsolv rewrites a .solv cache file, it reads directory-id values from the file's compressed filelist data without validating that they fall within the expected range. A corrupted or specially crafted .solv cache file (for example, one left in a torn state after an unclean system shutdown) can cause an out-of-bounds memory write when a tool such as dnf, yum, or zypper next processes it. Successful exploitation is expected to result in a crash of the affected tool (denial of service); it is not expected to allow arbitrary code execution because the out-of-bounds write always stores a fixed, non-attacker-controlled value.
- Product
- Red Hat Enterprise Linux 10
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Full record and what to do →NVD recordaccess.redhat.combugzilla.redhat.com
Aug 24, 2026Improper Neutralization of Special Elements used in an OS Command in the package manager component of Black Duck blackduck-c-cpp before 3.0.7 allows an actor abCVE-2026-76055 · Other software · Black Duck · reported by disclosure@synopsys.comHigh 7.5
Improper Neutralization of Special Elements used in an OS Command in the package manager component of Black Duck blackduck-c-cpp before 3.0.7 allows an actor able to create a file within the scanned build directory to execute operating system commands as the account running the scan. Filesystem paths encountered while traversing the scanned directory are interpolated into command strings that are executed through a shell without quoting or escaping, so shell metacharacters within those paths are interpreted rather than treated as literal text. No control over the build command or the tool's configuration is required.
- Product
- blackduck-c-cpp
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Full record and what to do →NVD recordcommunity.blackduck.compypi.org
Aug 20, 2026Nix is a package manager for Linux and other Unix systems.CVE-2026-64846 · Other software · NixOS · reported by GitHubLow 2.8
Nix is a package manager for Linux and other Unix systems. Prior to 2.35.0, a malicious derivation executed with the recursive-nix experimental feature can exploit a time-of-check/time-of-use race involving final symlink handling in the LocalStore restore path. The race can cause writeFile to follow a substituted final symlink when opening a path with O_TRUNC instead of enforcing FinalSymlink::DontFollow, allowing the Nix process or nix-daemon to create or truncate an empty file outside the build sandbox with the daemon user's permissions. The primitive does not provide arbitrary-content writes and requires winning the race. This issue is fixed in version 2.35.0.
- Product
- nix
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Aug 11, 2026Improper privilege management in Windows Package Manager allows an authorized attacker to elevate privileges locally.CVE-2026-68821 · Computers, phones & browsers · Microsoft · reported by secure@microsoft.comHigh 7.3
Improper privilege management in Windows Package Manager allows an authorized attacker to elevate privileges locally.
- Product
- App Installer
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Aug 5, 2026A flaw was found in the RPM Package Manager (RPM).CVE-2026-44605 · Other software · Red Hat · reported by Red HatMedium 5.5
A flaw was found in the RPM Package Manager (RPM). A local user could be affected by a heap buffer overflow vulnerability when processing a specially crafted NDB database file. This issue arises from an error in how RPM handles certain calculations during file parsing, leading to an incorrect memory allocation. An attacker could leverage this to cause a denial of service, making the system unavailable.
- Product
- Red Hat Hardened Images
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Full record and what to do →NVD recordaccess.redhat.comaccess.redhat.com
Jul 15, 2026Nixpkgs is a collection of software packages that can be installed with the Nix package manager.CVE-2026-61828 · Other software · NixOS · reported by GitHubHigh 8.5
Nixpkgs is a collection of software packages that can be installed with the Nix package manager. Prior to the 25.11 and 26.05 channel fixes, the NixOS module for MySQL services.mysql initializes the MySQL database in a way that allows local users, such as unprivileged web or CGI processes on the same host, to log in as the root user without a password when the service is used with mysql or percona-server. This issue is fixed in the 25.11 and 26.05.
- Product
- nixpkgs
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jul 6, 2026pnpm is a package manager.CVE-2026-59196 · Other software · pnpm · reported by GitHubHigh 7.1
pnpm is a package manager. Prior to 10.34.4 and 11.7.0, a crafted lockfile alias could be joined directly under a hoisted node_modules directory. Traversal aliases could escape that directory, while reserved aliases such as .bin or .pnpm could overwrite pnpm-owned layout. This vulnerability is fixed in 10.34.4 and 11.7.0.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jul 6, 2026pnpm is a package manager.CVE-2026-59195 · Other software · pnpm · reported by GitHubHigh 8.2
pnpm is a package manager. Prior to 10.34.4 and 11.8.0, pnpm accepts package names from the env lockfile configDependencies section and uses those names directly when creating config dependency symlinks under node_modules/.pnpm-config. A malicious repository can commit a crafted pnpm-lock.yaml whose env-lockfile document contains a traversal-shaped config dependency name. During pnpm install, pnpm installs the config dependency and creates a symlink at a path derived from that name. This vulnerability is fixed in 10.34.4 and 11.8.0.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jul 6, 2026pnpm is a package manager.CVE-2026-59194 · Other software · pnpm · reported by GitHubHigh 7.1
pnpm is a package manager. Prior to 10.34.4 and 11.7.0, a crafted patch entry could resolve outside the configured patches directory and cause pnpm patch-remove to delete an arbitrary reachable file. This vulnerability is fixed in 10.34.4 and 11.7.0.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jun 25, 2026pnpm is a package manager.CVE-2026-55700 · Other software · pnpm · reported by GitHubHigh 7.1
pnpm is a package manager. From 11.3.0 until 11.5.3, `pnpm stage download` derived a local filename from registry-controlled package name and version fields. A crafted manifest could escape the selected download directory and overwrite another reachable file. The merged fix validates both fields, derives one safe filename, and verifies the final destination before writing. This vulnerability is fixed in 11.5.3.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jun 25, 2026pnpm is a package manager.CVE-2026-55699 · Other software · pnpm · reported by GitHubMedium 6.5
pnpm is a package manager. Prior to 10.34.2 and 11.5.3, Manifest bin object keys such as "", ".", and ".." passed pnpm's bin-name guard. When a malicious package was installed globally, later global remove, update, or add-replacement flows could re-derive those names from the installed manifest and pass path.join(globalBinDir, binName) to removeBin. For "." this targets the global bin directory; for ".." this targets its parent. This vulnerability is fixed in 10.34.2 and 11.5.3.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jun 25, 2026pnpm is a package manager.CVE-2026-55698 · Other software · pnpm · reported by GitHubHigh 8.8
pnpm is a package manager. Prior to 10.34.2 and 11.5.3, pnpm can persist package-manager bootstrap metadata in the first YAML document of pnpm-lock.yaml. Before the patch, direct pnpm execution trusted an already resolved packageManagerDependencies entry when the committed env lockfile contained matching pnpm and @pnpm/exe versions. A malicious repository could therefore commit package-manager lockfile package records and snapshots that bypassed fresh package-manager resolution, then cause pnpm to install and execute bytes selected by that committed lockfile state during automatic version switching. This vulnerability is fixed in 10.34.2 and 11.5.3.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jun 25, 2026pnpm is a package manager.CVE-2026-55697 · Other software · pnpm · reported by GitHubHigh 7.5
pnpm is a package manager. Prior to 10.34.2 and 11.5.3, pnpm can install configDependencies declared in pnpm-workspace.yaml before command dispatch. Before the patch, a repository could declare pacquet or @pnpm/pacquet as a config dependency and pnpm treated that repository-controlled dependency as an install-engine opt-in. During install, pnpm resolved a platform-specific @pacquet/<platform>-<arch>/pacquet binary from node_modules/.pnpm-config/<packageName> and spawned it as the developer or CI user. This vulnerability is fixed in 10.34.2 and 11.5.3.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jun 25, 2026pnpm is a package manager.CVE-2026-55487 · Other software · pnpm · reported by GitHubHigh 7.5
pnpm is a package manager. Prior to 10.34.2 and 11.5.3, the generic peer-suffix normalizer also stripped parenthesized text from git, URL, tarball, file, and other opaque locators. Approval for one source string could therefore authorize a different attacker-controlled source whose locator normalized to the same value. This vulnerability is fixed in 10.34.2 and 11.5.3.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jun 25, 2026pnpm is a package manager.CVE-2026-55180 · Other software · pnpm · reported by GitHubMedium 6.5
pnpm is a package manager. Prior to 10.34.2 and 11.5.3, pnpm and pacquet expanded ${ENV_VAR} placeholders from repository-controlled .npmrc and pnpm-workspace.yaml into registry request destinations and registry credentials. A malicious repository could cause dependency resolution to send victim environment secrets to an attacker-selected registry before lifecycle scripts run. This vulnerability is fixed in 10.34.2 and 11.5.3.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jun 25, 2026pnpm is a package manager.CVE-2026-50573 · Other software · pnpm · reported by GitHubMedium 6.8
pnpm is a package manager. Prior to 10.34.0 and 11.4.0, `pnpm install` in non-frozen mode can accept new remote package content after detecting that the downloaded tarball does not match the integrity recorded in pnpm-lock.yaml. When a package is already locked with an integrity value, and the registry later serves different metadata and tarball content for the same package name and version, pnpm initially reports an integrity mismatch. However, plain pnpm install then performs a resolution repair, accepts the registry's new integrity, updates the lockfile, installs the new content, and exits successfully. This means the lockfile integrity check does not act as a hard stop by default. This vulnerability is fixed in 10.34.0 and 11.4.0.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jun 25, 2026pnpm is a package manager.CVE-2026-50021 · Other software · pnpm · reported by GitHubMedium 6.8
pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm's tarball extraction worker skips integrity verification when the integrity field is absent from the lockfile resolution. If an attacker can both modify pnpm-lock.yaml to remove the integrity: field and cause the referenced registry URL to serve altered package content, pnpm install --frozen-lockfile can install the altered package without an integrity error. npm's npm ci enforces integrity by default; pnpm's behavior of silently skipping verification is a pnpm-specific fail-open gap. This vulnerability is fixed in 10.34.0 and 11.4.0.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jun 25, 2026pnpm is a package manager.CVE-2026-50017 · Other software · pnpm · reported by GitHubMedium 6.9
pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm can send user-level unscoped npm authentication credentials to a registry chosen by a repository-local .npmrc file. In the reproduced case, the user's npm config contains a default registry and an unscoped _authToken. The repository does not provide a token-bearing auth line. It only sets registry= to a different registry URL. During normal pnpm metadata/install workflows, pnpm binds the user-origin unscoped credential to the repository-selected registry and sends it as an Authorization header. This vulnerability is fixed in 10.34.0 and 11.4.0.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jun 25, 2026pnpm is a package manager.CVE-2026-50016 · Other software · pnpm · reported by GitHubHigh 8.8
pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm allows a transitive dependency alias from registry package metadata to contain path traversal segments. During install, pnpm later uses that alias as a filesystem path when linking dependency nodes. As a result, a registry package can cause `pnpm install --ignore-scripts` to replace paths in the current project with symlinks to attacker-controlled dependency package directories. This vulnerability is fixed in 10.34.0 and 11.4.0.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jun 25, 2026pnpm is a package manager.CVE-2026-50015 · Other software · pnpm · reported by GitHubHigh 7.3
pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm's patch application pipeline (@pnpm/patch-package) performs no path validation on file paths extracted from .patch files. An attacker who contributes a malicious patch file via a pull request can write attacker-controlled content to or delete arbitrary files on the filesystem during pnpm install, as the user running the install. The diff --git header paths containing ../../ sequences traverse out of the package directory, and the traversal is difficult to catch in code review because patch file diff headers are opaque to most reviewers. This vulnerability is fixed in 10.34.0 and 11.4.0.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jun 25, 2026pnpm is a package manager.CVE-2026-50014 · Other software · pnpm · reported by GitHubMedium 6.4
pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm passes the lockfile-controlled git resolution.commit value to git fetch without a -- separator or commit-format validation. For git dependencies fetched through the shallow-fetch path, a malicious lockfile can replace the expected 40-character commit hash with a Git option such as --upload-pack=<command>. For SSH and local transports, --upload-pack can execute the supplied command. HTTPS transports ignore --upload-pack, so the practical attack surface is primarily SSH or local git dependencies. This vulnerability is fixed in 10.34.0 and 11.4.0.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jun 25, 2026pnpm is a package manager.CVE-2026-48995 · Other software · pnpm · reported by GitHubMedium 4.8
pnpm is a package manager. Prior to 10.33.4 and 11.0.7, a malicious codeload.github.com server can serve whatever tarball it wants and pnpm will install it regardless of the lockfile. The lockfile does not store the hash of the dependencies from https://codeload.github.com. This means that if this server was compromised or a person's machine configuration was compromised, pnpm would download and install these dependencies. This vulnerability is fixed in 10.33.4 and 11.0.7.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jun 17, 2026In Package Manager, there is a possible device lock controller bypass due to a missing permission check.CVE-2026-0092 · Computers, phones & browsers · Google · reported by security@android.comCritical 10
In Package Manager, there is a possible device lock controller bypass due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
- Product
- Android
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Apr 9, 2026Helm is a package manager for Charts for Kubernetes.CVE-2026-35206 · Other software · helm · reported by GitHubMedium 4.8
Helm is a package manager for Charts for Kubernetes. In Helm versions <=3.20.1 and <=4.1.3, a specially crafted Chart will cause helm pull --untar [chart URL | repo/chartname] to write the Chart's contents to the immediate output directory (as defaulted to the current working directory; or as given by the --destination and --untardir flags), rather than the expected output directory suffixed by the chart's name. This vulnerability is fixed in 3.20.2 and 4.1.4.
- Product
- helm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Apr 9, 2026oma is a package manager for AOSC OS.CVE-2026-39958 · Other software · AOSC-Dev · reported by GitHubMedium 5.2
oma is a package manager for AOSC OS. Prior to 1.25.2, oma-topics is responsible for fetching metadata for testing repositories (topics) named "Topic Manifests" ({mirror}/debs/manifest/topics.json) from remote repository servers, registering them as APT source entries. However, the name field in said metadata were not checked for transliteration. In this case, a malicious party may supply a malformed Topic Manifest, which may cause malicious APT source entries to be added to /etc/apt/sources.list.d/atm.list as oma-topics finishes fetching and registering metadata. This vulnerability is fixed in 1.25.2.
- Product
- oma
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Apr 9, 2026Helm is a package manager for Charts for Kubernetes.CVE-2026-35205 · Other software · helm · reported by GitHubHigh 8.4
Helm is a package manager for Charts for Kubernetes. From 4.0.0 to 4.1.3, Helm will install plugins missing provenance (.prov file) when signature verification is required. This vulnerability is fixed in 4.1.4.
- Product
- helm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Apr 9, 2026Helm is a package manager for Charts for Kubernetes.CVE-2026-35204 · Other software · helm · reported by GitHubHigh 8.4
Helm is a package manager for Charts for Kubernetes. From 4.0.0 to 4.1.3, a specially crafted Helm plugin, when installed or updated, will cause Helm to write the contents of the plugin to an arbitrary filesystem location. To prevent this, validate that the plugin.yaml of the Helm plugin does not include a version: field containing POSIX dot-dot path separators ie. "/../". This vulnerability is fixed in 4.1.4.
- Product
- helm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Apr 8, 2026Nix is a package manager for Linux and other Unix systems.CVE-2026-39860 · Other software · NixOS · reported by GitHubCritical 9
Nix is a package manager for Linux and other Unix systems. A bug in the fix for CVE-2024-27297 allowed for arbitrary overwrites of files writable by the Nix process orchestrating the builds (typically the Nix daemon running as root in multi-user installations) by following symlinks during fixed-output derivation output registration. This affects sandboxed Linux builds - sandboxed macOS builds are unaffected. The location of the temporary output used for the output copy was located inside the build chroot. A symlink, pointing to an arbitrary location in the filesystem, could be created by the derivation builder at that path. During output registration, the Nix process (running in the host mount namespace) would follow that symlink and overwrite the destination with the derivation's output contents. In multi-user installations, this allows all users able to submit builds to the Nix daemon (allowed-users - defaulting to all users) to gain root privileges by modifying sensitive files. This vulnerability is fixed in 2.34.5, 2.33.4, 2.32.7, 2.31.4, 2.30.4, 2.29.3, and 2.28.6.
- Product
- nix
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Apr 1, 2026An unauthenticated remote code execution (RCE) vulnerability exists in applications that use the Replicator node package manager (npm) version 1.0.5 to deserialCVE-2026-2265 · Other software · Replicator · reported by cret@cert.orgMedium 6.5
An unauthenticated remote code execution (RCE) vulnerability exists in applications that use the Replicator node package manager (npm) version 1.0.5 to deserialize untrusted user input and execute the resulting object.
- Product
- Replicator
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 30, 2026vcpkg is a free and open-source C/C++ package manager.CVE-2026-34054 · Computers, phones & browsers · microsoft · reported by GitHubHigh 7.8
vcpkg is a free and open-source C/C++ package manager. Prior to version 3.6.1#3, vcpkg's Windows builds of OpenSSL set openssldir to a path on the build machine, making that path be attackable later on customer machines. This issue has been patched in version 3.6.1#3.
- Product
- vcpkg
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jan 26, 2026pnpm is a package manager.CVE-2026-24131 · Other software · pnpm · reported by GitHubMedium 6.7
pnpm is a package manager. Prior to version 10.28.2, when pnpm processes a package's `directories.bin` field, it uses `path.join()` without validating the result stays within the package root. A malicious npm package can specify `"directories": {"bin": "../../../../tmp"}` to escape the package directory, causing pnpm to chmod 755 files at arbitrary locations. This issue only affects Unix/Linux/macOS. Windows is not affected (`fixBin` gated by `EXECUTABLE_SHEBANG_SUPPORTED`). Version 10.28.2 contains a patch.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jan 26, 2026pnpm is a package manager.CVE-2026-24056 · Other software · pnpm · reported by GitHubMedium 6.7
pnpm is a package manager. Prior to version 10.28.2, when pnpm installs a `file:` (directory) or `git:` dependency, it follows symlinks and reads their target contents without constraining them to the package root. A malicious package containing a symlink to an absolute path (e.g., `/etc/passwd`, `~/.ssh/id_rsa`) causes pnpm to copy that file's contents into `node_modules`, leaking local data. The vulnerability only affects `file:` and `git:` dependencies. Registry packages (npm) have symlinks stripped during publish and are NOT affected. The issue impacts developers installing local/file dependencies andCI/CD pipelines installing git dependencies. It can lead to credential theft via symlinks to `~/.aws/credentials`, `~/.npmrc`, `~/.ssh/id_rsa`. Version 10.28.2 contains a patch.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jan 26, 2026pnpm is a package manager.CVE-2026-23890 · Other software · pnpm · reported by GitHubMedium 6.5
pnpm is a package manager. Prior to version 10.28.1, a path traversal vulnerability in pnpm's bin linking allows malicious npm packages to create executable shims or symlinks outside of `node_modules/.bin`. Bin names starting with `@` bypass validation, and after scope normalization, path traversal sequences like `../../` remain intact. This issue affects all pnpm users who install npm packages and CI/CD pipelines using pnpm. It can lead to overwriting config files, scripts, or other sensitive files. Version 10.28.1 contains a patch.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jan 26, 2026pnpm is a package manager.CVE-2026-23889 · Other software · pnpm · reported by GitHubMedium 6.5
pnpm is a package manager. Prior to version 10.28.1, a path traversal vulnerability in pnpm's tarball extraction allows malicious packages to write files outside the package directory on Windows. The path normalization only checks for `./` but not `.\`. On Windows, backslashes are directory separators, enabling path traversal. This vulnerability is Windows-only. This issue impacts Windows pnpm users and Windows CI/CD pipelines (GitHub Actions Windows runners, Azure DevOps). It can lead to overwriting `.npmrc`, build configs, or other files. Version 10.28.1 contains a patch.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jan 26, 2026pnpm is a package manager.CVE-2026-23888 · Other software · pnpm · reported by GitHubMedium 6.5
pnpm is a package manager. Prior to version 10.28.1, a path traversal vulnerability in pnpm's binary fetcher allows malicious packages to write files outside the intended extraction directory. The vulnerability has two attack vectors: (1) Malicious ZIP entries containing `../` or absolute paths that escape the extraction root via AdmZip's `extractAllTo`, and (2) The `BinaryResolution.prefix` field is concatenated into the extraction path without validation, allowing a crafted prefix like `../../evil` to redirect extracted files outside `targetDir`. The issue impacts all pnpm users who install packages with binary assets, users who configure custom Node.js binary locations and CI/CD pipelines that auto-install binary dependencies. It can lead to overwriting config files, scripts, or other sensitive files leading to RCE. Version 10.28.1 contains a patch.
- Product
- pnpm
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Where this comes from: the exploited list is CISA’s Known Exploited Vulnerabilities catalog. Everything else is the whole National Vulnerability Database, where each record is published by the team that found the bug (Wordfence, Patchstack, WPScan, the vendors themselves and others); we show who. Exploit odds are FIRST’s EPSS, updated daily. Titles and categories are ours, so check the linked record before acting on a detail. For a write-up of the big ones, see our advisories. Every vendor, and every WordPress plugin and theme with a recorded flaw, also has its own page. All of it is free to reuse as JSON, CSV or RSS.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.