{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34590 exists.","fix":"No fix has been published for CVE-2026-34590 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34590 is a medium-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-34590 and fix it if it is affected.\n\nWhat it is: CVE-2026-34590 is a medium-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-34590 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-34590/ (Markdown: https://insights.sbomify.com/CVE-2026-34590/index.md)","id":"CVE-2026-34590","markdown":"https://insights.sbomify.com/CVE-2026-34590/index.md","name":"CVE-2026-34590","record":{"aliases":["GHSA-wc9c-7cv8-m225"],"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":"Attackers can exploit missing URL validation in webhook creation to perform blind SSRF against internal services in Postiz.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"postiz","vendor":"gitroom"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Postiz is an AI social media scheduling tool. Prior to version 2.21.4, the POST /webhooks/ endpoint for creating webhooks uses WebhooksDto which validates the url field with only @IsUrl() (format check), missing the @IsSafeWebhookUrl validator that blocks internal/private network addresses. The update (PUT /webhooks/) and test (POST /webhooks/send) endpoints correctly apply @IsSafeWebhookUrl. When a post is published, the orchestrator fetches the stored webhook URL without runtime validation, enabling blind SSRF against internal services. This issue has been patched in version 2.21.4.","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 via Webhook Creation Endpoint Missing URL Safety Validation","id":"CVE-2026-34590","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Poetry Has Wheel Path Traversal Which Can Lead to Arbitrary File Write","id":"CVE-2026-34591"},"packages":[],"prev":{"headline":"OpenEXR: DWA Lossy Decoder Heap Out-of-Bounds Write","id":"CVE-2026-34589"},"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.3,"headline":"Postiz: SSRF in upload-from-url endpoint allows fetching internal resources and cloud metadata","id":"CVE-2026-34576","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"}],"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-03","vendors":["gitroomhq"]},"summary":"Attackers can exploit missing URL validation in webhook creation to perform blind SSRF against internal services in Postiz.","url":"https://insights.sbomify.com/CVE-2026-34590/"}