# CVE-2026-119746: ProSoft ICX35 Login Lockout Bypass via Client-Side Cookies


- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 4 Nov 2026
- **Also known as:** GHSA-g6fw-2m44-gprg

## What is CVE-2026-119746?

CVE-2026-119746 is a high-severity vulnerability in ProSoft Technology ICX35-HWC-E, published on 4 Nov 2026. 

### Official description

ProSoft Technology ICX35 devices (X35-HWC-A and ICX35-HWC-E) contain a login lockout bypass in the integrated module web page. The account lockout mechanism that restricts repeated failed authentication attempts is enforced in client-side JavaScript, so a remote attacker can reset the lockout and continue submitting password guesses by deleting the relevant browser cookies, defeating the brute-force protection. This vulnerability has been addressed in version 1.14.158.

Weakness: CWE-602 (Client-Side Enforcement of Server-Side Security), CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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


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

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

## Is CVE-2026-119746 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119746 is a high-severity vulnerability in ProSoft Technology ICX35-HWC-E, published on 4 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-119746 in the wild and no public exploit code.

Affected product: ProSoft Technology ICX35-HWC-E. 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-119746/ (Markdown: https://insights.sbomify.com/CVE-2026-119746/index.md)
```

## Sources

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

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