# CVE-2026-27546: Authentication Bypass in _account_log

> Unauthenticated attackers can bypass authentication in industrial I/O modules to gain admin access, posing a risk to operational technology environments.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-pvrf-wj35-pxjx

## What is CVE-2026-27546?

CVE-2026-27546 is a critical authentication bypass vulnerability in Carlo Gavazzi Automation ICE2-8IOL-G65L-V1D, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated remote attacker can exploit an authentication bypass in the _account_log function to log in as an admin, even when accounts are properly configured.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

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

## Is CVE-2026-27546 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-27546 is a critical authentication bypass vulnerability in Carlo Gavazzi Automation ICE2-8IOL-G65L-V1D, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-27546 in the wild and no public exploit code.

Affected product: Carlo Gavazzi Automation ICE2-8IOL-G65L-V1D. 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-27546/ (Markdown: https://insights.sbomify.com/CVE-2026-27546/index.md)
```

## Sources

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

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