# CVE-2025-65328: Security feature bypass in n/a

> Attackers can spoof client IP addresses via X-Forwarded-For headers to bypass IP-based security controls in Mega-Fence deployments relying on this value.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jan 2026
- **Updated:** 5 Jan 2026
- **Also known as:** GHSA-6gh2-xjvw-7rh4

## What is CVE-2025-65328?

CVE-2025-65328 is a medium-severity vulnerability in n/a, published on 5 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mega-Fence (webgate-lib.*) 25.1.914 and prior trusts the first value of the X-Forwarded-For (XFF) header as the client IP without validating a trusted proxy chain. An attacker can supply an arbitrary XFF value in a remote request to spoof the client IP, which is then propagated to security-relevant state (e.g., WG_CLIENT_IP cookie). Deployments that rely on this value for IP allowlists may be bypassed.

Weakness: CWE-807 (Reliance on Untrusted Inputs in a Security Decision)

## Which versions are affected by CVE-2025-65328?

It affects 1 product.


Products: Mega-Fence Project Mega-Fence.

## How do I fix CVE-2025-65328?

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

## Is CVE-2025-65328 being exploited?

There is no known exploitation of CVE-2025-65328 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-65328 and fix it if it is affected.

What it is: CVE-2025-65328 is a medium-severity vulnerability in n/a, published on 5 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-65328 in the wild and no public exploit code.

Affected product: n/a. 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-2025-65328/ (Markdown: https://insights.sbomify.com/CVE-2025-65328/index.md)
```

## Sources

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

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