# CVE-2026-40463: An Insufficient Role-based Access Control Vulnerability in WaveSuite

> Authenticated low-privilege users can access restricted log file pages by directly requesting URLs, bypassing role-based access controls.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L`)
- **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:** 31 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-wf77-f5jc-xpcv

## What is CVE-2026-40463?

CVE-2026-40463 is a high-severity missing authorization vulnerability in Nokia WaveSuite, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

WaveSuite is affected by an insufficient role-based access control vulnerability in the CPB Log Files feature. Successful exploitation allows an authenticated low-privilege user to load pages restricted to higher-privilege roles by requesting the corresponding URL directly in the browser.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-40463 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40463 is a high-severity missing authorization vulnerability in Nokia WaveSuite, published on 31 Aug 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-40463 in the wild and no public exploit code.

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

## Sources

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

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