# CVE-2026-67442: FUXA Business Logic Flaw: Role Deletion Without User Assignment Cleanup

> Deleting a role in FUXA fails to remove it from user assignments, allowing users to retain revoked permissions and bypass access controls.

- **Severity:** Low 2.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-cqww-jqx5-p32v

## What is CVE-2026-67442?

CVE-2026-67442 is a low-severity vulnerability in frangoteam FUXA, published on 18 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. Prior to 1.3.3, DELETE /api/roles removes role definitions through server/runtime/users/usrstorage.js but does not remove the deleted role identifier from each user's info.roles array or the runtime usersMap cache. If a permission configuration still references that identifier, an affected user can retain authorization rights that an administrator intended to revoke, causing residual privilege, inconsistent access-control state, and misleading audit results. This issue is fixed in version 1.3.3.

Weakness: CWE-459 (Incomplete Cleanup), CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-67442 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67442 is a low-severity vulnerability in frangoteam FUXA, published on 18 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-67442 in the wild and no public exploit code.

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

## Sources

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

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