NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
CRITICAL severity

CVE-2022-38916 — pagekit

CRITICAL

CVE-2022-38916 is a critical-severity (CVSS 9.8) Unrestricted File Upload vulnerability in pagekit/pagekit. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Pagekit vulnerable to Unrestricted Upload of File with Dangerous Type

Also known asGHSA-4v5m-vwvp-p7w8
Published
Updated
Affected
1 pkg
Patched
See advisory
Exploits
1 known
Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-38916.

EPSS Exploitation Probability

via FIRST.org ↗
18.3%probability of exploitation in next 30 days
Moderate Risk+0.40%
Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk
0.00%7.90%15.8%23.7%0.5%18.3%May 26Aug 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐘pagekit/pagekit

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

Description

A file upload vulnerability exists in the storage feature of pagekit 1.0.18, which allows an attacker to upload malicious files

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🐘Packagistpagekit/pagekitall versionsNo fix

Affected Products

1 product · 1 configurations
Application
pagekitpagekit
1 version
1.0.18
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 pagekit/pagekit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    The records we use list no patched version of pagekit/pagekit for CVE-2022-38916. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

  3. Mitigate without a patch

    Treat uploaded files as untrusted until proven otherwise: validate the actual content type rather than the supplied extension, store uploads outside the web root on a volume mounted without execute permission, and rename them to server-generated identifiers so an attacker cannot choose the path a request will later resolve.

Frequently Asked Questions

A file upload vulnerability exists in the storage feature of pagekit 1.0.18, which allows an attacker to upload malicious files
O3 Security · Impact-Aware SCA

Is CVE-2022-38916 in your dependencies?

Find it across Packagist, including transitive dependencies.

CVE-2022-38916: pagekit (Critical 9.8)