# CVE-2026-116054: SH3 Módulo de Gestão/Módulo de Arrecadação weak password hash


- **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-hrh2-6gcc-h3rw

## What is CVE-2026-116054?

CVE-2026-116054 is a low-severity vulnerability in SH3, published on 25 Oct 2026. 

### Official description

A security vulnerability has been detected in SH3. This affects an unknown function of the component Módulo de Gestão/Módulo de Arrecadação. The manipulation leads to password hash with insufficient computational effort. The attack is possible to be carried out remotely. A high degree of complexity is needed for the attack. The exploitability is reported as difficult. The exploit has been disclosed publicly and may be used. Upgrading to version 2026.0.2.0 mitigates this issue. Upgrading the affected component is recommended.

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort), CWE-326 (Inadequate Encryption Strength)

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


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

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

## Is CVE-2026-116054 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116054 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116054 is a low-severity vulnerability in SH3, published on 25 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116054 exists.

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

## Sources

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

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