Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

CVE-2020-7674

CRITICAL

CVE-2020-7674 is a critical-severity (CVSS 9.8) Code Injection vulnerability in access-policy. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2020-7674 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Improper Input Validation in access-policy

Also known asGHSA-fw2f-7f87-5r6cSNYK-JS-ACCESSPOLICY-571490
Published
Jun 10, 2020
Updated
Jul 9, 2026
Affected
1 pkg
Patched
None yet
Exploits
1 known
Exploitation data as of Jul 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
📦access-policy

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

access-policy through 3.1.0 is vulnerable to Arbitrary Code Execution. User input provided to the template function is executed by the eval function resulting in code execution.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmaccess-policyall versionsNo fix
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for access-policy. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of access-policy has shipped for CVE-2020-7674 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2020-7674 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2020-7674. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

access-policy through 3.1.0 is vulnerable to Arbitrary Code Execution. User input provided to the `template` function is executed by the `eval` function resulting in code execution.
O3 Security · Impact-Aware SCA

Is CVE-2020-7674 in your dependencies?

O3 detects CVE-2020-7674 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

CVE-2020-7674: Improper Input Validation in… | O3 Security