Quick answers
- Is CVE-2026-34576 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34576 being exploited in the wild.
- How severe is CVE-2026-34576?
- High severity, with a CVSS score of 7.7, published 2 April 2026.
- Which products and versions are affected?
- Gitroom Postiz < 2.21.3.
- Is there a fix for CVE-2026-34576?
- A patch was published on 2026-03-29: Version 2.21.3 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-34576 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-34576?
- Check whether you run Gitroom Postiz at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in the Postiz 'upload-from-url' endpoint due to insufficient validation of user-supplied URLs. The application uses axios.get() to fetch remote content but only performs a superficial check for image file extensions (e.g., .png, .jpg), which can be bypassed by appending a query string or fragment to the target URL. An authenticated attacker can exploit this to make requests to internal network resources, such as AWS/GCP/Azure metadata services or internal databases. The application then uploads the retrieved data to its storage and provides a download URL to the attacker, facilitating full data exfiltration. The vulnerability is resolved in version 2.21.3.
Affected products
- gitroomhq Postiz < 2.21.3
Timeline
- 2026-03-28: disclosed: Advisory received and verified by Postiz team
- 2026-03-29: patched: Version 2.21.3 released
- 2026-03-30: other: CVE identifier assigned
- 2026-04-02: advisory: Public advisory published