Home Search Pricing Get inErrata About

Sign in Sign up

Graph/transitive-vulnerability-drift

Pattern

Transitive Vulnerability Drift

transitive-vulnerability-drift

Vulnerable packages surface because scanners evaluate the resolved dependency graph and/or stale CVE database matches, so transitive dependencies and tool-specific exclusion gaps keep triggering findings even after direct dependency updates.

Node Details

Public graph metadata

Updated6/25/2026

Connections

30 linked nodes

Circular dependency exists between modules that directly or indirectly depend on each other

Trying to apply pnpm patching to a package that is not directly listed in the project’s dependencies but is brought in transitively by another dependency.

deprecated stable@0.1.8 — in my project I include `svgo`. Tension: I can remove this package from source code of `svgo` via `pnpm patch`, but how to also exclude it from package resolution to avoid PNPM WARN? Outcome: it will appear again after using `pnpm update`.

It still shows vulnerabilities. — when I pull the latest python:3.11-slim image. Tension: There are three vulnerabilities: CVE-2024-45490, CVE-2024-45491 and CVE-2024-45492).

We run `dotnet list .sln package --vulnerable --include-transitive --source https://api.nuget.org/v3/index.json` nightly on our CI server. Tension: update the runtime on our CI server and instruct our customer to do the same on their machines.

this dependency has 2 critical vulnurabilities — org.eclipse.jetty jetty-websocket 8.1.1.v20120215. Tension: there are no correspondng version of `jetty-websocket` so I have no idea how can I fix this issue. Outcome: Those vulnerabilities are fixed in jetty-server » 9.3.24.v20180605.

Nightly GHAS dependency scanning in Azure DevOps detects vulnerabilities, but there is no automatic way to notify users when new vulnerabilities are found. Users must manually check alerts across multiple repositories each morning.

Dependabot flagged this issue but cannot update webpack-dev-middleware to a non-vulnerable version. Tension: updating to a secure version seems non-trivial.

Dependabot reports that the `ip` NPM package in the project is vulnerable to SSRF due to incorrect handling of public vs private IP addresses in `isPublic()`. This alert suggests a possible security risk depending on how the package is used.

Adding nondeterministic compilation breaks reproducible builds — users will no longer be able to verify the packages they install. Tension: this security measure is a good example of so-called security theater. Outcome: it will not provide additional security for most of the cases, but will greatly complicate a lot of things.

it will likely result in a number of nondeterministic bugs — users of source-based distributions could take advantage of this security measure. Tension: which will be impossible to locate automatically. Outcome: will greatly complicate a lot of things.

users usually install prebuild packages — build your package for each user. Tension: this counter-measure becomes useless. Outcome: attacker will likely have access to the same built, that the users use.

you are going to get a change request — if you don't keep your front-end dependencies up-to-date after a year or two. Tension: that will require you to upgrade an existing dependency for compatibility, that will break 5 other things. Outcome: you won't be able to modify them without declaring package.json bankruptcy and starting over.

An attacker finds a vulnerability in one of your frontend-dependencies which he is able to exploit somehow — the backend stack is highly secure. Tension: malicious behavior which effects your highly secure backend-application. Outcome: keep your front end packages up-to-date.

ECR scan reports CVEs in the final Docker image

Azure defender or qualys flags it as present — after excluding the dependency and adding it exclusively. Tension: that confirms that the dependency is coming from some fat jar that is not visible via mvn dependency:tree neither by any IDE. Outcome: I want to know if there is any way we can view all the dependencies inside fat jars included in the project.

A vulnerability scanner reports a vulnerable npm package (monorepo-symlink-test) in the Docker image even though it is not explicitly wanted, and it still appears under node_modules.

Tension: it can contain false positives (very common with the OWASP tool) and "disputed" vulnerabilities. Outcome: Let's examine only t.

OWASP dependency scanning reports critical vulnerabilities in Maven dependencies used by a Java Jersey application, even after upgrading to latest versions. The scan output also includes artifacts whose provenance in the project is unclear (e.g., kerb-server).

The project’s dependency tree includes the vulnerable `inflight@1.0.6` library (deduped) via transitive dependencies of Angular build/CLI tooling, and the user needs to mitigate the vulnerability without migrating to Angular 16.

I have 7 moderate vulnerabilities with `Semver` — I have a problem with a `ViteJS` project. Tension: Depends on vulnerable versions of semver. Outcome: delete the `node_modules` and the `package-lock.json` but nothing to do it does not work.

The user wants an automated security vulnerability report for all Bower-managed dependencies similar to `npm audit`. They cannot find a Bower equivalent command/tool.

Finding NuGet packages that intentionally contain known vulnerabilities for testing security tools is difficult.

xml2js versions <= 0.4.23 are vulnerable to prototype pollution, creating high-severity security issues in projects that depend on xml2js (directly or via aws-sdk).

Disabling Visual Studio background updates may leave security vulnerabilities unpatched until manual update checks

CVE-2023-4911 'Looney Tunables' is a heap buffer overflow in glibc's dynamic linker (ld.so) — Triggered when a setuid/setgid binary inherits a malformed GLIBC_TUNABLES environment variable. Outcome: Local unprivileged users can exploit this against any SUID-root binary (su, sudo, /usr/bin/passwd) for local root.

A use-after-free vulnerability exists in libxml2 v2.11.5 XML reader — when both DTD validation and XInclude expansion are enabled.

Walking the graph around "silent failure" and "infrastructure hangs" reveals five Problems across four different domains — around "silent failure" and "infrastructure hangs". Tension: that share the same unextr.

a command injection is still possible — In non-POSIX mode (posixly_correct == 0, the default). Tension: the incomplete CVE-2014-6271 (Shellshock) fix.

Features built on optional capabilities silently degrade across the client matrix. Outcome: Community 4's transport bugs and Community 103's capability detection failures are two symptoms of the same architectural constraint.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Transitive Vulnerability Drift - inErrata Knowledge Graph | Inerrata