{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-53536 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-53536 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-53536 is a medium-severity missing authorization vulnerability in activepieces, published on 16 Jul 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-53536 and fix it if it is affected.\n\nWhat it is: CVE-2026-53536 is a medium-severity missing authorization vulnerability in activepieces, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-53536 in the wild and no public exploit code.\n\nAffected product: activepieces. 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-53536/ (Markdown: https://insights.sbomify.com/CVE-2026-53536/index.md)","id":"CVE-2026-53536","markdown":"https://insights.sbomify.com/CVE-2026-53536/index.md","name":"CVE-2026-53536","record":{"aliases":["GHSA-9723-fmff-mc24"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"AI workflow automation","requires_auth":"low_privilege","summary":"Authenticated users can download step-files from other tenants due to missing JWT audience validation and null checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"Activepieces is an open source AI workflow automation platform. Prior to 0.83.0, the /v1/step-files/signed download endpoint verified the supplied JWT against the shared signing secret but did not check the token's audience, and combined with a missing null-check on the decoded fileId, this allowed any caller holding any valid Activepieces JWT (including a freshly created user's own access token) to receive a step-file belonging to another tenant. The file returned was whatever PostgreSQL happened to scan first for type = FLOW_STEP_FILE, varying over time as the database changed, so an authenticated user could obtain step-file attachments belonging to other tenants on the same instance; the attacker could not target a specific victim or file, and the access was read-only with no integrity or availability impact. This issue is fixed in version 0.83.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Activepieces: Cross-tenant file download via missing JWT audience check on step-files signed URL","id":"CVE-2026-53536","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Python-Multipart: Content-Disposition parameter smuggling via RFC 2231/5987 extended parameters","id":"CVE-2026-53537"},"packages":[],"prev":{"headline":"Activepieces: Arbitrary file write in git-sync via path traversal and symlinks","id":"CVE-2026-53535"},"products":["activepieces"],"published":"2026-07-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-18","vendors":["activepieces"]},"summary":"Authenticated users can download step-files from other tenants due to missing JWT audience validation and null checks.","url":"https://insights.sbomify.com/CVE-2026-53536/"}