# CVE-2026-12718: SQLi in Karel Electronics' KarelIPS

> Blind SQL injection in KarelIPS allows attackers to read database contents; the product is unsupported and requires replacement.

- **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:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-9524-7567-6c47

## What is CVE-2026-12718?

CVE-2026-12718 is a critical SQL injection vulnerability in KarelIPS, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper neutralization of special elements used in an SQL command ('SQL injection') vulnerability in Karel Electronic Industry and Trade Inc. KarelIPS allows Blind SQL Injection.

This issue affects KarelIPS: through 22092026.
NOTE: The vendor was contacted and it was learned that the product is not supported.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2026-12718 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12718 is a critical SQL injection vulnerability in KarelIPS, published on 22 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-12718 in the wild and no public exploit code.

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

## Sources

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

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