# CVE-2026-113507: aaPanel common.py GetClientIp access control


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-vvxf-x39h-gvfp

## What is CVE-2026-113507?

CVE-2026-113507 is a medium-severity vulnerability in aaPanel, published on 20 Oct 2026. 

### Official description

A vulnerability was found in aaPanel up to 8.25.0. The impacted element is the function GetClientIp of the file class/public/common.py. The manipulation of the argument X-Real-Ip results in improper access controls. The attack may be performed from remote. The exploit has been made public and could be used. The vendor confirms: "The reported X-Real-Ip IP-bypass vulnerability has already been fixed".

Weakness: CWE-284 (Improper Access Control), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-113507 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113507 is a medium-severity vulnerability in aaPanel, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113507 exists.

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

## Sources

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

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