{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34576 exists.","fix":"No fix has been published for CVE-2026-34576 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34576 is a high-severity server-side request forgery vulnerability in gitroomhq postiz-app, published on 2 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-34576 and fix it if it is affected.\n\nWhat it is: CVE-2026-34576 is a high-severity server-side request forgery vulnerability in gitroomhq postiz-app, published on 2 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34576 exists.\n\nAffected product: gitroomhq postiz-app. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-34576/ (Markdown: https://insights.sbomify.com/CVE-2026-34576/index.md)","id":"CVE-2026-34576","markdown":"https://insights.sbomify.com/CVE-2026-34576/index.md","name":"CVE-2026-34576","record":{"aliases":["GHSA-89vp-m2qw-7v34"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Social media scheduling tool","requires_auth":"low_privilege","summary":"An authenticated user can exploit an SSRF vulnerability in the upload-from-url endpoint to access internal network resources and cloud metadata.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"postiz","vendor":"gitroom"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Postiz is an AI social media scheduling tool. Prior to version 2.21.3, the POST /public/v1/upload-from-url endpoint accepts a user-supplied URL and fetches it server-side using axios.get() with no SSRF protections. The only validation is a file extension check (.png, .jpg, etc.) which is trivially bypassed by appending an image extension to any URL path. An authenticated API user can fetch internal network resources, cloud instance metadata, and other internal services, with the response data uploaded to storage and returned to the attacker. This issue has been patched in version 2.21.3.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Postiz: SSRF in upload-from-url endpoint allows fetching internal resources and cloud metadata","id":"CVE-2026-34576","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Postiz: Unauthenticated Full-Read SSRF via /public/stream Endpoint with Trivially Bypassable Extension Check","id":"CVE-2026-34577"},"packages":[],"prev":{"headline":"Parse Server: Session field immutability bypass via falsy-value guard","id":"CVE-2026-34574"},"products":["postiz-app"],"published":"2026-04-02","related":[{"cvss_score":10,"headline":"Postiz: Arbitrary Code Execution and Token Exfiltration in pr-docker-build.yml via untrusted Dockerfile.dev","id":"CVE-2026-42298","kev_date_added":null,"published":"2026-05-08"},{"cvss_score":8.9,"headline":"Postiz stored XSS in public preview page","id":"CVE-2026-42556","kev_date_added":null,"published":"2026-05-08"},{"cvss_score":8.9,"headline":"Postiz Has Unrestricted File Upload via MIME Type Spoofing that Leads to Stored XSS","id":"CVE-2026-40487","kev_date_added":null,"published":"2026-04-18"},{"cvss_score":8.6,"headline":"Postiz: Unauthenticated Full-Read SSRF via /public/stream Endpoint with Trivially Bypassable Extension Check","id":"CVE-2026-34577","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":8.2,"headline":"Postiz has Server-Side Request Forgery via Redirect Bypass in /api/public/stream","id":"CVE-2026-40168","kev_date_added":null,"published":"2026-04-10"},{"cvss_score":5.4,"headline":"Postiz: SSRF via Webhook Creation Endpoint Missing URL Safety Validation","id":"CVE-2026-34590","kev_date_added":null,"published":"2026-04-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-02","vendors":["gitroomhq"]},"summary":"An authenticated user can exploit an SSRF vulnerability in the upload-from-url endpoint to access internal network resources and cloud metadata.","url":"https://insights.sbomify.com/CVE-2026-34576/"}