# CVE-2026-34577: Postiz SSRF in PublicController stream endpoint

Source: https://junglewise.ai/threats/cve-2026-34577-postiz-ssrf-in-publiccontroller-stream-endpoint  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-02. Updated: 2026-07-24  
License: CC BY 4.0 with a link back

CVE-2026-34577 · Severity: high · CVSS 8.6 · Published 2026-04-02

Postiz, an AI-powered social media scheduling tool, contains a security flaw in its public media streaming component. An unauthenticated attacker can use this flaw to trick the server into accessing and returning data from internal systems that are not supposed to be reachable from the internet. This could lead to the theft of sensitive cloud credentials, exposure of internal databases, and unauthorized access to private company data.

Technologies: [Gitroom Postiz](https://junglewise.ai/threats/technologies/postiz). Vendors: [Gitroom](https://junglewise.ai/threats/vendors/gitroom).

## Quick answers

**Is CVE-2026-34577 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-34577 being exploited in the wild.

**How severe is CVE-2026-34577?** High severity, with a CVSS score of 8.6, published 2 April 2026.

**Which products and versions are affected?** Gitroom Postiz < 2.21.3.

**Is there a fix for CVE-2026-34577?** A patch was published on 2026-03-29: Version 2.21.3 released with security fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-34577 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-34577?** 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 `PublicController` of Postiz due to insufficient validation of the `url` parameter in the `GET /public/stream` endpoint. The application attempts to restrict requests by checking if the URL ends with '.mp4', but this is easily bypassed by appending '.mp4' as a dummy query parameter or fragment (e.g., `http://internal-service/.mp4`). Because the application proxies the full HTTP response back to the requester without authentication or network-level restrictions, an attacker can perform full-read SSRF. This allows for the retrieval of sensitive data from internal network resources, such as cloud metadata services (AWS/GCP/Azure) and internal databases. The vulnerability is resolved in version 2.21.3.

## Affected products

- gitroomhq Postiz < 2.21.3

## Timeline

- 2026-03-28: disclosed: Initial report received by vendor
- 2026-03-29: patched: Version 2.21.3 released with security fix
- 2026-04-02: advisory: CVE-2026-34577 published

## References

- [https://github.com/gitroomhq/postiz-app/releases/tag/v2.21.3](https://github.com/gitroomhq/postiz-app/releases/tag/v2.21.3)
- [https://github.com/gitroomhq/postiz-app/security/advisories/GHSA-mv6h-v3jg-g539](https://github.com/gitroomhq/postiz-app/security/advisories/GHSA-mv6h-v3jg-g539)

## Related threats

- [Gitroomhq Postiz authorization bypass in Nowpayments webhook](https://junglewise.ai/threats/cve-2026-48799-gitroomhq-postiz-authorization-bypass-in-nowpayments-webhook)
- [Postiz billing enforcement bypass in modify-subscription endpoint](https://junglewise.ai/threats/cve-2026-48783-postiz-billing-enforcement-bypass-in-modify-subscription-endpoint)
- [Postiz privilege escalation via JWT forgery in Skool integration](https://junglewise.ai/threats/cve-2026-48781-postiz-privilege-escalation-via-jwt-forgery-in-skool-integration)
- [Gitroom Postiz stored XSS in public preview page](https://junglewise.ai/threats/cve-2026-42556-gitroom-postiz-stored-xss-in-public-preview-page)
- [Postiz SSRF via DNS Rebinding TOCTOU in URL Validation](https://junglewise.ai/threats/cve-2026-42346-postiz-ssrf-via-dns-rebinding-toctou-in-url-validation)