Cyber Resilience

CVE-2025-61985

Published
06 October 2025
Modified
14 July 2026
CVSS Score v3.1 3.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS Score 0.0011 2th percentile
Risk Priority 28 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-61985 is a low-severity Improper Neutralization of Null Byte or NUL Character (CWE-158) vulnerability in Marc (inferred from references). Its CVSS base score is 3.6 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

ssh in OpenSSH before 10.1 allows the '\0' character in an ssh:// URI, potentially leading to code execution when a ProxyCommand is used.

CWE(s)
CWE-158

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2009-1537Shared CWE-158
CVE-2023-5719Shared CWE-158
CVE-2025-66263Shared CWE-158
CVE-2024-10921Shared CWE-158
CVE-2026-4359Shared CWE-158
CVE-2026-43861Shared CWE-158
CVE-2025-14388Shared CWE-158
CVE-2025-55113Shared CWE-158
CVE-2026-23863Shared CWE-158
CVE-2024-0408Shared CWE-158

Affected Assets

Marc
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.10

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Input validation directly requires neutralizing or rejecting malformed characters such as NUL before they reach downstream components.

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-06 mostly match
prevents

Secure SDLC practices directly require input neutralization and validation to prevent null-byte flaws.

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.29 Security testing in development and acceptance mostly match
finds

Security testing can detect null-byte flaws but does not itself implement the neutralization.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and sanitization that directly prevents null-byte injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements include explicit rules for neutralizing dangerous characters such as NUL.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the likelihood of unsafe data flows but do not prescribe character neutralization.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly require proper neutralization of null bytes and other metacharacters.

References