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

> Misconfiguration in Foundry Container Service allows cross-pod communication and local command execution, bypassing network boundaries.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2025
- **Updated:** 18 Dec 2025
- **Also known as:** GHSA-627q-2hvv-p867

## What is CVE-2025-53710?

CVE-2025-53710 is a high-severity vulnerability in com.palantir.codeassist2:code-assist-proxy, published on 18 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-653 (Improper Isolation or Compartmentalization)

## Which versions are affected by CVE-2025-53710?


## How do I fix CVE-2025-53710?

No fix has been published for CVE-2025-53710 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-53710 being exploited?

There is no known exploitation of CVE-2025-53710 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53710 and fix it if it is affected.

What it is: CVE-2025-53710 is a high-severity vulnerability in com.palantir.codeassist2:code-assist-proxy, published on 18 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-53710 in the wild and no public exploit code.

Affected product: com.palantir.codeassist2:code-assist-proxy. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-53710/ (Markdown: https://insights.sbomify.com/CVE-2025-53710/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-53710
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-53710
- OSV: https://osv.dev/vulnerability/CVE-2025-53710

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-53710/
Summaries are generated and may contain mistakes; the official description above is the record.