# CVE-2025-27926: Hardcoded credentials in Automation

> Unauthorized users can read passwords from configuration files in Nintex Automation, leading to potential data exposure and security bypass.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2025
- **Updated:** 11 Mar 2025
- **Also known as:** GHSA-h2w7-2v8j-jgm7

## What is CVE-2025-27926?

CVE-2025-27926 is a medium-severity vulnerability in Nintex Automation, published on 10 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Nintex Automation 5.6 and 5.7 before 5.8, the K2 SmartForms Designer folder has configuration files (web.config) containing passwords that are readable by unauthorized users.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Nintex Automation.

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

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

## Is CVE-2025-27926 being exploited?

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

## Other vulnerabilities in Nintex Automation

- [CVE-2025-27925](https://insights.sbomify.com/CVE-2025-27925/): Deserialization in Automation (high 8.5)
- [CVE-2025-27924](https://insights.sbomify.com/CVE-2025-27924/): Cross-site scripting in Automation (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27926 is a medium-severity vulnerability in Nintex Automation, published on 10 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-27926 in the wild and no public exploit code.

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

## Sources

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

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