# CVE-2025-26849: Hardcoded credentials in Docusnap

> Attackers can decrypt sensitive inventory files containing firewall rules using a hard-coded cryptographic key in Docusnap.

- **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:** 4 Mar 2025
- **Updated:** 5 Mar 2025
- **Also known as:** GHSA-rgwp-j8mq-fhc5

## What is CVE-2025-26849?

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

### Official description

There is a Hard-coded Cryptographic Key in Docusnap 13.0.1440.24261, and earlier and later versions. This key can be used to decrypt inventory files that contain sensitive information such as firewall rules.

Weakness: CWE-1394 (Use of Default Cryptographic Key)

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

It affects 1 product.


Products: Docusnap Docusnap.

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

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

## Is CVE-2025-26849 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-26849 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-26849 is a medium-severity vulnerability in Docusnap, published on 4 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-26849 exists.

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

## Sources

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

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