Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

CVE-2021-4162 — archivy

MEDIUMFix: archivy/archivy@796c3ae

CVE-2021-4162 is a medium-severity (CVSS 4.3) Cross-Site Request Forgery (CSRF) vulnerability in archivy. 1 public exploit reference exists, so weaponization risk is real. A fix is available for archivy — see the affected versions and patch details below.

archivy is vulnerable to Cross-Site Request Forgery (CSRF)

Also known asGHSA-9236-8w7q-rmrvPYSEC-2021-869
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs30th percentile — riskier than 30% of all scored CVEsHighest risk
0.00%0.29%0.59%0.88%0.1%0.4%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2021-4162 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
🐍archivy

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

Description

archivy is vulnerable to Cross-Site Request Forgery (CSRF). There is a fix available in the master branch.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIarchivyall versions1.6.2pip install --upgrade 'archivy==1.6.2'

Affected Products

1 product · 1 configurations
Application
archivyarchivy_project
≤ 1.6.1
range
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.

archivy is vulnerable to Cross-Site Request Forgery (CSRF)

huntr.devNVDJan 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for archivy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update archivy to 1.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-4162 is resolved across your whole dependency graph.

  3. Workarounds

    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.

Frequently Asked Questions

archivy is vulnerable to Cross-Site Request Forgery (CSRF). There is [a fix](https://github.com/archivy/archivy/commit/796c3ae318eea183fc88c87ec5a27355b0f6a99d) available in the master branch.
O3 Security · Impact-Aware SCA

Is CVE-2021-4162 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2021-4162: archivy CSRF — Fixed in 1.6.2