# CVE-2026-11849: IEI Integration Corp｜iRM-IEI Remote Management - Hard-coded Credentials

> Unauthenticated remote attackers can use hard-coded credentials to gain administrative privileges on the database of IEI Integration Corp's iRM-IEI Remote Management system.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2026
- **Updated:** 12 Jun 2026
- **Also known as:** GHSA-ccm4-vchx-9cmq

## What is CVE-2026-11849?

CVE-2026-11849 is a critical vulnerability in IEI Integration Corp iRM-TSi410X, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 
iRM-IEI Remote Management developed by IEI Integration Corp has a Hardcoded Credentials vulnerability, allowing unauthenticated remote attackers to exploit hard-coded credentials to gain administrative privileges on the database.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2026-11849 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11849 is a critical vulnerability in IEI Integration Corp iRM-TSi410X, published on 12 Jun 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-11849 in the wild and no public exploit code.

Affected product: IEI Integration Corp iRM-TSi410X. 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-11849/ (Markdown: https://insights.sbomify.com/CVE-2026-11849/index.md)
```

## Sources

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

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