Cyber Resilience

CVE-2026-10223

Published
01 June 2026
Modified
22 July 2026
CVSS Score v4 2.1
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0023 14th percentile
Risk Priority 15 floored blend · peak EPSS

Summary

CVE-2026-10223 is a low-severity Injection (CWE-74) vulnerability. Its CVSS base score is 2.1 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 14th 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) and SC-7 (Boundary Protection) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

A weakness has been identified in NousResearch hermes-agent up to 2026.4.30. This affects the function _scan_memory_content of the file tools/memory_tool.py. This manipulation causes injection. The attack can be initiated remotely. The exploit has been made available to the public and…

more

could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

CWE(s)
CWE-74CWE-707

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

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 →
T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
Why these techniques?

Remote injection vulnerability (CWE-74) directly enables T1190 (public-facing app exploitation) and T1659 (content injection).

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-10222Shared CWE-707, CWE-74
CVE-2026-0865Shared CWE-74
CVE-2026-2954Shared CWE-707, CWE-74
CVE-2025-9797Shared CWE-707, CWE-74
CVE-2024-10491Shared CWE-74
CVE-2026-7045Shared CWE-707, CWE-74
CVE-2026-9353Shared CWE-707, CWE-74
CVE-2026-9420Shared CWE-707, CWE-74
CVE-2026-6994Shared CWE-707, CWE-74
CVE-2026-3992Shared CWE-707, CWE-74

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-10 Information Input Validation
  • SC-7 Boundary Protection
Detect
Catch it (NIST detect / respond)
  • SI-7 Software, Firmware, and Information Integrity
Harden
Shrink the surface (DISA STIG)
  • 6 hardening rules · 4 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V1.3.9
  • V1.2.1
  • V1.2.3
  • V1.2.5

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match
prevent

Directly enforces validation and sanitization of untrusted memory content passed to _scan_memory_content, blocking the CWE-74 injection vector before execution.

SI-7 Software, Firmware, and Information Integrity partial match
detect

Requires integrity verification of software and data, enabling detection of unauthorized code or command insertion resulting from the memory-tool injection.

SC-7 Boundary Protection partial match
prevent

Restricts remote network access paths that could deliver crafted input to the vulnerable hermes-agent memory scanning function.

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 validation and output encoding that prevent injection 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.28 Secure coding mostly match
prevents

Secure coding standards directly require proper neutralization of inputs and outputs, eliminating CWE-707.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development catches injection vulnerabilities before release.

A.8.15 Logging partial match
detects

Logging supports detection of injection attempts but does not prevent the weakness.

A.8.16 Monitoring activities partial match
detects

Monitoring activities can identify active injection attacks after they occur.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and output encoding that directly prevent injection flaws.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against injection attacks in software design.

References