How severe is GHSA-vj2p-7pgw-g2wf?

GHSA-vj2p-7pgw-g2wf has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-vj2p-7pgw-g2wf?

GHSA-vj2p-7pgw-g2wf affects the following packages: postiz (npm). Ecosystems affected: npm.

How do I fix GHSA-vj2p-7pgw-g2wf?

The records we use list no patched version of postiz for GHSA-vj2p-7pgw-g2wf. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-vj2p-7pgw-g2wf in my npm dependencies?

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.

How do I mitigate GHSA-vj2p-7pgw-g2wf if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is GHSA-vj2p-7pgw-g2wf actively exploited in the wild?

No public exploit code has been indexed for GHSA-vj2p-7pgw-g2wf yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-vj2p-7pgw-g2wf published, and has it been updated?

GHSA-vj2p-7pgw-g2wf was published on March 27, 2026 and was last updated on March 27, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

HIGH severity

Postiz App has a High-Severity SSRF Vulnerability via Next.jsGHSA-vj2p-7pgw-g2wf

HIGH

GHSA-vj2p-7pgw-g2wf is a high-severity (CVSS 7.5) vulnerability in postiz. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

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

7Kdownloads / 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

Ecosystem	Package	Vulnerable range	Fix
📦npm	`postiz`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

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.
Remediation status
The records we use list no patched version of postiz for GHSA-vj2p-7pgw-g2wf. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

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?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works