# CVE-2025-68609: Authentication bypass in Aries due to misconfiguration

> Unauthenticated attackers can bypass authentication to view system logs and perform management operations on Palantir Aries instances.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2026
- **Updated:** 22 Jan 2026
- **Also known as:** GHSA-73vg-mq6j-x5w2

## What is CVE-2025-68609?

CVE-2025-68609 is a medium-severity authentication bypass vulnerability in com.palantir.aries:aries, published on 22 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability in Palantir's Aries service allowed unauthenticated access to log viewing and management functionality on Apollo instances using default configuration. The defect resulted in both authentication and authorization checks being bypassed, potentially allowing any network-accessible client to view system logs and perform operations without valid credentials. No evidence of exploitation was identified during the vulnerability window.

Weakness: CWE-305 (Authentication Bypass by Primary Weakness)

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


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

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

## Is CVE-2025-68609 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68609 is a medium-severity authentication bypass vulnerability in com.palantir.aries:aries, published on 22 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68609 in the wild and no public exploit code.

Affected product: com.palantir.aries:aries. 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-68609/ (Markdown: https://insights.sbomify.com/CVE-2025-68609/index.md)
```

## Sources

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

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