# CVE-2026-74047: Wazuh 4.0.0 before 4.14.8 authd.pass Disclosure via Agent 000 Config Endpoint

> Low-privileged users can retrieve the plaintext enrollment password from the manager, allowing rogue agent registration.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-qj8j-r988-54rx

## What is CVE-2026-74047?

CVE-2026-74047 is a high-severity vulnerability in wazuh-manager, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Wazuh from 4.0.0 before 4.14.8 contains an information disclosure vulnerability that allows low-privileged users with agent:read to retrieve the plaintext authd.pass enrollment password via the unmasked agent configuration endpoint. Attackers holding the default readonly role can request the auth component configuration for pseudo-agent ID 000 to obtain the secret and enroll rogue agents against the manager.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-74047 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74047 is a high-severity vulnerability in wazuh-manager, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-74047 exists.

Affected product: wazuh-manager. 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-74047/ (Markdown: https://insights.sbomify.com/CVE-2026-74047/index.md)
```

## Sources

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

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