# CVE-2026-92256: Netcore NR255-V 1.5.130703 IPsec PSK and RSA Key Disclosure via l2tpd_config_show.cgi Read Handlers

> Attackers can retrieve stored IPsec PSK and RSA keys from Netcore NR255-V routers via exposed CGI handlers, compromising VPN security.

- **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:** 15 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-wfrq-fmxh-g284

## What is CVE-2026-92256?

CVE-2026-92256 is a high-severity vulnerability in Netcore NR255-V, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

NR255-V version 1.5.130703 contains a sensitive information disclosure vulnerability in l2tpd_config_show_cgi.c, ipsec_show_cgi.c, and mod_vpn_remote/plan.json read handlers. Attackers can query l2tpd_config_show.cgi to expose stored IPsec PSK and RSA key material.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2026-92256 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92256 is a high-severity vulnerability in Netcore NR255-V, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92256 in the wild and no public exploit code.

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

## Sources

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

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