# CVE-2026-118376: WeKnora before 0.8.2 SSRF Guard Bypass via NAT64 IPv6 Addresses


- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-29gq-28qv-vr5m

## What is CVE-2026-118376?

CVE-2026-118376 is a medium-severity vulnerability in Tencent WeKnora, published on 28 Oct 2026. 

### Official description

WeKnora before 0.8.2 contains a server-side request forgery vulnerability in isRestrictedIP() that misclassifies NAT64-prefixed IPv6 addresses as public. Authenticated attackers can supply URLs resolving to NAT64 encodings of internal addresses via web_fetch or URL-based knowledge import to reach internal services or cloud metadata endpoints.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-118376 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-118376 is a medium-severity vulnerability in Tencent WeKnora, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118376 in the wild and no public exploit code.

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

## Sources

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

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