Quick answers
- Is CVE-2026-40168 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-40168 being exploited in the wild.
- How severe is CVE-2026-40168?
- High severity, with a CVSS score of 8.2, published 10 April 2026.
- Which products and versions are affected?
- Gitroom Postiz < 2.21.5.
- Is there a fix for CVE-2026-40168?
- A patch was published on 2026-04-09: Version 2.21.5 released. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-40168 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-40168?
- Check whether you run Gitroom Postiz. 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 `/api/public/stream` endpoint of Postiz due to insufficient validation of HTTP redirects. While the application performs an initial check to block internal or private IP addresses, it does not perform subsequent validation if the initial public URL redirects the request. An unauthenticated attacker can exploit this by providing a URL they control that redirects to internal resources, such as cloud metadata services (169.254.169.254) or internal APIs. This can lead to internal network scanning, interaction with unauthenticated internal services, and potential exposure of cloud credentials. The vulnerability is patched in version 2.21.5.
Affected products
- Gitroom Postiz < 2.21.5
Timeline
- 2026-04-03: disclosed: Postiz received the initial report.
- 2026-04-09: patched: Version 2.21.5 released.
- 2026-04-10: advisory: CVE-2026-40168 published.