# CVE-2025-3831: Exposed SFTP server

> Unauthorized parties could access sensitive log files uploaded by the Harmony SASE agent due to an exposed SFTP server.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2025
- **Updated:** 12 Aug 2025
- **Also known as:** GHSA-c4ph-52m2-gvc6

## What is CVE-2025-3831?

CVE-2025-3831 is a high-severity vulnerability in checkpoint Check Point Harmony SASE, published on 12 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Log files uploaded during troubleshooting by the Harmony SASE agent may have been accessible to unauthorized parties.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Checkpoint Harmony Sase.

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

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

## Is CVE-2025-3831 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3831 is a high-severity vulnerability in checkpoint Check Point Harmony SASE, published on 12 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3831 in the wild and no public exploit code.

Affected product: checkpoint Check Point Harmony SASE. 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-3831/ (Markdown: https://insights.sbomify.com/CVE-2025-3831/index.md)
```

## Sources

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

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