Skip to main content
VulnerabilityPublished

CVE-2026-34576: gitroomhq postiz-app · Server-Side Request Forgery (SSRF)

Affects gitroomhq postiz-appSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.3 High : upgrade to 2.21.3 soon.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 4.0 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.21.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade postiz-app and gitroomhq/postiz-app to 2.21.3.

Affected software

ProductAffectedFixed in
gitroomhqpostiz-appAffected
  • <2.21.3
Fixed in
  • 2.21.3
GitHubgitroomhq/postiz-apppkg:github/gitroomhq/postiz-appOther threatsAffected
  • <2.21.3
Fixed in
  • 2.21.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade postiz-app to version 2.21.3 or later, where this SSRF vulnerability has been patched. No other mitigations are specified or required once the official fix is applied.

Description

CVE-2026-34576 is a Server-Side Request Forgery (SSRF) vulnerability in the gitroomhq postiz-app prior to version 2.21.3. The vulnerable endpoint POST /public/v1/upload-from-url accepts a user-supplied URL and fetches it server-side without proper SSRF protections, relying only on a weak file extension check that can be bypassed. An authenticated API user can exploit this to access internal network resources, cloud instance metadata, and other internal services. The issue has been patched in version 2.21.3.

References

Community reviews

Loading reviews…