# CVE-2026-7112: NousResearch hermes-agent API_SERVER_KEY api_server.py _check_auth improper authentication

> Remote attackers can bypass authentication in the hermes-agent API server due to improper checks, potentially gaining unauthorized access.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Apr 2026
- **Updated:** 27 Apr 2026
- **Also known as:** GHSA-r7hr-pvjh-r4p3

## What is CVE-2026-7112?

CVE-2026-7112 is a medium-severity authentication bypass vulnerability in NousResearch hermes-agent, published on 27 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been found in NousResearch hermes-agent 0.8.0. Affected by this vulnerability is the function _check_auth of the file gateway/platforms/api_server.py of the component API_SERVER_KEY Handler. The manipulation leads to improper authentication. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through a pull request but has not reacted yet.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-7112?


## How do I fix CVE-2026-7112?

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

## Is CVE-2026-7112 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7112 and fix it if it is affected.

What it is: CVE-2026-7112 is a medium-severity authentication bypass vulnerability in NousResearch hermes-agent, published on 27 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7112 exists.

Affected product: NousResearch hermes-agent. 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-2026-7112/ (Markdown: https://insights.sbomify.com/CVE-2026-7112/index.md)
```

## Sources

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

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