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

GHSA-vj2p-7pgw-g2wf postiz

HIGH

GHSA-vj2p-7pgw-g2wf is a high-severity (CVSS 7.5) vulnerability in postiz. No vendor fix is recorded yet; mitigation options are listed below.

Postiz App has a High-Severity SSRF Vulnerability via Next.js

Published
Mar 27, 2026
Updated
Mar 27, 2026
Affected
1 pkg
Patched
None yet
Exploits
None indexed
Exploitation data as of Mar 27, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
postiznpm
3Kdownloads / week

Description

Impact

A successful SSRF attack allows an attacker to:

  • Bypass firewalls to scan and interact with internal network services/ports.
  • Access sensitive cloud metadata services (e.g., AWS IMDS 169.254.169.254) to potentially leak instance credentials.
  • Pivot into the internal network environment where Postiz is hosted.

Workarounds

There are no workarounds known to this, please upgrade to Postiz version v2.21.1.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmpostizall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Remediation status

    No patched version of postiz has shipped for GHSA-vj2p-7pgw-g2wf 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vj2p-7pgw-g2wf can be triaged on real exposure rather than presence alone.

Tailored to GHSA-vj2p-7pgw-g2wf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact A successful SSRF attack allows an attacker to: - Bypass firewalls to scan and interact with internal network services/ports. - Access sensitive cloud metadata services (e.g., AWS IMDS 169.254.169.254) to potentially leak instance credentials. - Pivot into the internal network environment where Postiz is hosted. ### Workarounds There are no workarounds known to this, please upgrade to Postiz version `v2.21.1`.
O3 Security · Impact-Aware SCA

Is GHSA-vj2p-7pgw-g2wf in your dependencies?

O3 Security finds GHSA-vj2p-7pgw-g2wf across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-vj2p-7pgw-g2wf: postiz SSRF (High 7.5) | O3 Security