# CVE-2026-116471: BKWLD Decoy Authorization Policy Policy.php privileges management


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-4294-m2vx-p5cx

## What is CVE-2026-116471?

CVE-2026-116471 is a medium-severity vulnerability in BKWLD Decoy, published on 26 Oct 2026. 

### Official description

A security flaw has been discovered in BKWLD Decoy up to 5.11.1. The impacted element is an unknown function of the file Policy.php of the component Authorization Policy. The manipulation of the argument role results in improper privilege management. The attack may be performed from remote. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-269 (Improper Privilege Management), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-116471 being exploited?

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

Public exploit code:

- Security research and documentation for BKWLD Decoy 5.11.1 — CVE-2026-116471. (github_poc): https://github.com/solo506/bkwld-decoy-cve-2026-116471

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116471 is a medium-severity vulnerability in BKWLD Decoy, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116471 in the wild and no public exploit code.

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

## Sources

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

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