Tested

npm audit still flags Effect CVE-2026-121707 through Prisma

If npm audit keeps flagging effect after an update, check which package requires the affected version. In our standalone npm fixture, prisma@7.10.1 installed @prisma/config@7.10.1, which requires exactly effect@3.20.0. Updating Effect left the exact pin in place. The GitHub reviewed advisory for CVE-2026-121707 lists 3.22.1 as the first patched Effect release. GitHub reviewed advisory · Prisma config 7.10.1 registry metadata

Trace the installed copy

Run these from the npm project that owns the lockfile used by your failing job. For a workspace, start at the root that owns the audited lockfile. If a Docker migration stage installs Prisma with a separate manifest, inspect that stage's dependency tree too.

npm explain effect
npm ls effect --all
npm audit --json

npm explain shows who requires the installed copy. npm ls helps find multiple versions. In the audit JSON, find the GHSA ID in the advisory URL under vulnerabilities.effect.via and check nodes for the installed paths. npm may also report parent packages that inherit the finding. In our fixture, the three entries were effect, @prisma/config and prisma. All three came from GHSA-7589-6fvf-x4pw.

The maintainers published their advisory on 4 November. GitHub published the reviewed database entry on 19 November. It lists Effect through 3.22.0, with 3.22.1 as the first patched release. Check the current entry and your audit output when choosing a version. Maintainer advisory · GitHub Advisory Database

Check whether Prisma has moved the pin

Use the installed versions from the tree and check published registry metadata for the Prisma release you intend to install. These commands show the exact fixture release and a Prisma 6 example.

npm view prisma@7.10.1 dependencies.@prisma/config
npm view @prisma/config@7.10.1 dependencies.effect
npm view @prisma/config@6.19.3 dependencies.effect

The first two returned 7.10.1 and 3.20.0. Config 6.19.3 returned 3.21.0. Prisma 7.10.1 and 6.19.3 were the newest stable releases in their major lines on 20 November. The npm latest tag pointed to a Prisma 8 release candidate. Check the version you intend to deploy and its own dependency tree. If a compatible Prisma release in your supported line resolves a patched Effect version, update Prisma to that release and rerun your original audit. Prisma 7.10.1 registry metadata · Prisma config 6.19.3 registry metadata · Prisma npm dist-tags · Prisma issue

In our fixture, npm update effect --ignore-scripts --no-audit left Effect at 3.20.0. The audit JSON's fixAvailable field named Prisma 6.12.0 and marked the change as semver-major. Review the exact change proposed by your own audit before accepting it. A Prisma downgrade can change your application and migration workflow.

Override a single transitive Effect copy

Use the override below only in a standalone npm project where npm ls effect --all shows exactly one Effect copy and npm explain effect traces it only through @prisma/config from Prisma. Check that your manifest has no direct Effect dependency. We tested Prisma and Config at 7.10.1. The first command sets the nested effect value under overrides → @prisma/config. If something already overrides that dependency, inspect the existing rule before changing it. npm overrides documentation · Effect 3.22.5 registry metadata

If your project uses npm workspaces or declares Effect directly, stop after diagnosis. In those test setups an install with the override could exit successfully while the Prisma copy stayed on 3.20.0. Use the tree and the relevant manifests to check each dependency path, including any Effect requirement in your own package.json.

npm pkg set 'overrides.@prisma/config.effect=3.22.5'
npm install --ignore-scripts
npm ls effect --all
npm audit --json

Before keeping the change, check that npm ls effect --all exits 0 and shows effect@3.22.5 as overridden under @prisma/config. Run your original audit with the same options and scope. Confirm that its completed report no longer lists GHSA-7589-6fvf-x4pw. If either check fails, stop and inspect the remaining dependency path. Read the manifest and lockfile diff once both checks pass.

Verify the resulting lockfile with a clean install. Use the original audit tool, policy and scope to check the result in CI.

npm ci --ignore-scripts
npm ls effect --all
npm audit --json

For a separate deploy or migration install, trace the copy with that install’s package manager and rerun its original scan in the same environment.

The example installs with lifecycle scripts disabled to check resolution. Run your usual application checks before shipping, including Prisma configuration, generation and migration validation if those are part of your workflow. Once your supported Prisma release carries the fixed dependency, remove the temporary override, regenerate the lockfile and check again.

What the fixture showed

We ran these commands with Node.js 22.23.4 and npm 10.9.9 in a digest-pinned official Linux image. The fixture has one direct dependency, Prisma 7.10.1. We checked Effect's version in the lockfile and on disk after each audit.

StageInstalled Effectnpm package findingsAudit exit
Initial install3.20.031
After updating Effect under the original parent pin3.20.031
After the scoped override3.22.500
After a clean lockfile install3.22.500
After another Effect update with the override in place3.22.500

The fixture covers npm resolution and advisory reporting. Application compatibility, migration behavior and exposure in a deployed build require their own checks.

The audit identifies packages and versions to investigate. To assess application exposure, check where the shipped code calls the affected Effect schema and whether it processes untrusted input there. A remaining advisory on a different dependency can keep the overall audit red.

Use your package audit to verify the Effect result. The Breakage Calendar checker looks for other dated changes in a repository folder. Check your repository for other dated changes

Corrections can be sent to hello@cybernative.ai. We publish dated corrections.