Cyber Resilience

CVE-2025-26849

Docusnap ≤ 13.0.1440.24261

Public PoC
Published
04 March 2025
Modified
07 July 2025
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
EPSS Score 0.0024 16th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-26849 is a medium-severity Use of Default Cryptographic Key (CWE-1394) vulnerability in Docusnap Docusnap. Its CVSS base score is 4.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Private Keys (T1552.004); ranked at the 16th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and SC-12 (Cryptographic Key Establishment and Management) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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.

CWE(s)
CWE-1394

Related Threats

MITRE ATT&CK Enterprise Techniques

T1552.004 Private Keys Credential Access
Adversaries may search for private key certificate files on compromised systems for insecurely stored credentials.
attack.mitre.org →
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-5039Shared CWE-1394
CVE-2024-11619Shared CWE-1394
CVE-2026-54887Shared CWE-1394
CVE-2026-2215Shared CWE-1394
CVE-2025-41744Shared CWE-1394
CVE-2024-48956Shared CWE-1394
CVE-2026-20709Shared CWE-1394
CVE-2025-44954Shared CWE-1394
CVE-2024-1275Shared CWE-1394
CVE-2025-41742Shared CWE-1394

Affected Assets

docusnap
docusnap
≤ 13.0.1440.24261

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SC-12 Cryptographic Key Establishment and Management good match

Cryptographic key establishment and management requires generating and provisioning unique keys rather than relying on manufacturer defaults.

CM-6 Configuration Settings good match

Requiring the most restrictive configuration settings prohibits the use of known default cryptographic keys.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-01 mostly match
prevents

Configuration management directly prohibits default keys via hardened baselines and change control.

PR.AA-01 partial match
prevents

Credential/key management practices eliminate default cryptographic keys for identities and services.

PR.AA-03 partial match
prevents

Strong authentication requirements implicitly disallow default keys but do not address key management itself.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.24 Use of cryptography mostly match
prevents

Mandates proper key management, directly preventing use of default cryptographic keys.

A.8.9 Configuration management mostly match
prevents

Enforces secure configuration baselines that should replace default keys.

A.8.19 Installation of software on operational systems partial match
prevents

Controls software installation and configuration, reducing risk of default keys being left in place.

A.8.32 Change management partial match
prevents

Change-management processes should detect and remediate default cryptographic keys.

A.8.5 Secure authentication none match
none

Requires secure authentication mechanisms that would be undermined by default keys.

References