{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-53709 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-53709 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-53709 is a medium-severity missing authorization vulnerability in com.palantir.secupload:secure-upload, published on 10 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-53709 and fix it if it is affected.\n\nWhat it is: CVE-2025-53709 is a medium-severity missing authorization vulnerability in com.palantir.secupload:secure-upload, published on 10 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-53709 in the wild and no public exploit code.\n\nAffected product: com.palantir.secupload:secure-upload. 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-2025-53709/ (Markdown: https://insights.sbomify.com/CVE-2025-53709/index.md)","id":"CVE-2025-53709","markdown":"https://insights.sbomify.com/CVE-2025-53709/index.md","name":"CVE-2025-53709","record":{"aliases":["GHSA-jqrw-5fq8-4hx8"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Palantir Foundry secure-upload","requires_auth":"low_privilege","summary":"Privileged users could modify submission channels and unauthenticated users could enumerate enrollments due to missing authorization checks in the secure-upload service.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Palantir","cpe":[],"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-285","name":"Improper Authorization"}],"description":"Secure-upload is a data submission service that validates single-use tokens when accepting submissions to channels. The service only installed on a small number of environments.\n\nUnder specific circumstances, privileged users of secure-upload could have selected email templates not necessarily created for their enrollment when sending data upload requests.\nAuthenticated and privileged users of one enrollment could have abused an endpoint to redirect existing submission channels to a dataset they control.\nAn endpoint handling domain validation allowed unauthenticated users to enumerate existing enrollments.\nFinally, other endpoints allowed enumerating if a resource with a known RID exists across enrollments.\n\nThe affected service has been patched with version 0.815.0 and automatically deployed to all Apollo-managed Foundry instances.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Access control issues impacting secure-upload service","id":"CVE-2025-53709","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Network boundaries not respected in certain Foundry namespaces.","id":"CVE-2025-53710"},"packages":[],"prev":{"headline":"Cross-site scripting in MedDream PACS Premium","id":"CVE-2025-53707"},"products":["com.palantir.secupload:secure-upload"],"published":"2025-07-10","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":"2025-07-10","vendors":["Palantir"]},"summary":"Privileged users could modify submission channels and unauthenticated users could enumerate enrollments due to missing authorization checks in the secure-upload service.","url":"https://insights.sbomify.com/CVE-2025-53709/"}