dbcve.org
InjectionWeakness · CWE-74

CVE-2026-10222

MEDIUM · 5.6 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A security flaw has been discovered in NousResearch hermes-agent up to 2026.4.30. Affected by this issue is the function _sanitize_env_lines of the file hermes_cli/config.py. The manipulation results in injection. It is possible to launch the attack remotely. The attack requires a high level of complexity. The exploitation is known to be difficult. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An injection vulnerability exists in the _sanitize_env_lines function in hermes_cli/config.py of NousResearch hermes-agent. The function, responsible for sanitizing environment variables, fails to properly validate or escape input, allowing injection of malicious environment variable content. This could allow an attacker to influence application behavior through crafted environment variables.

MitigationImplement robust input validation and sanitization in the _sanitize_env_lines function to prevent injection of special characters or malicious environment variable assignments. Consider using allowlist validation for permitted characters and patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm hermes-agent installation
    Run 'pip show hermes-agent' or check your package manager for the installed nousresearch-hermes-agent package and note the version number
    Affected if The package is installed and the version falls within any vulnerable range (compare to released fixed versions when available)
  2. Locate vulnerable config.py file
    Find hermes_cli/config.py in your hermes-agent installation directory (typically in site-packages or the source repository)
    Affected if The file exists and contains the _sanitize_env_lines function
  3. Inspect _sanitize_env_lines function
    Open hermes_cli/config.py and examine the _sanitize_env_lines function for proper input sanitization logic (look for missing validation, allowlist checks, or dangerous character handling)
    Affected if The function lacks adequate sanitization of environment variable names or values before processing
  4. Identify environment variable input sources
    Review how environment variables are passed to the application (check startup scripts, API calls, configuration files, or user-supplied input that gets converted to env vars)
    Affected if Untrusted or user-controlled input can influence environment variables passed to hermes-agent
  5. Check for untrusted input paths
    Trace the data flow from external input sources to the _sanitize_env_lines function - examine any endpoints, APIs, or configuration loaders that accept external data
    Affected if External or untrusted input can reach the vulnerable function without validation

You are affected if hermes-agent is installed, the _sanitize_env_lines function lacks proper sanitization, and untrusted input can influence environment variables processed by the application.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement robust input validation and sanitization in the _sanitize_env_lines function to prevent injection of special characters or malicious environment variable assignments. Consider using allowlist validation for permitted characters and patterns.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10222 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10222 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data