# CVE-2025-41659: CODESYS Control PKI Exposure Enables Remote Certificate Access

> A low-privileged attacker can remotely read and write PKI certificates and keys in CODESYS Control, enabling data extraction or trust manipulation.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **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:** 4 Aug 2025
- **Updated:** 4 Aug 2025
- **Also known as:** GHSA-x97q-fjxx-pvxm

## What is CVE-2025-41659?

CVE-2025-41659 is a high-severity vulnerability in CODESYS Control RTE (SL), published on 4 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A low-privileged attacker can remotely access the PKI folder of the CODESYS Control runtime system and thus read and write certificates and its keys. This allows sensitive data to be extracted or to accept certificates as trusted. Although all services remain available, only unencrypted communication is possible if the certificates are deleted.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

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

## Is CVE-2025-41659 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41659 is a high-severity vulnerability in CODESYS Control RTE (SL), published on 4 Aug 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-41659 in the wild and no public exploit code.

Affected product: CODESYS Control RTE (SL). 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-41659/ (Markdown: https://insights.sbomify.com/CVE-2025-41659/index.md)
```

## Sources

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

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