TR-CERT Warns of Critical SQL Injection in Unsupported KarelIPS

P1 — VALIDATE AND UPDATECritical · 9.8 (CVSS v3.1)EXPLOITATION: NOT STATED

Quick Answer

TR-CERT reports unauthenticated blind SQL injection in KarelIPS through its listed 22092026 identifier. The vendor confirmed the product is unsupported, and the record names no fixed release. Restrict exposure and plan retirement or replacement; an ordinary patch rollout is not an established remedy.

Confirm Scope And Plan Replacement

What to do now: Locate KarelIPS instances and their database connections, restrict access to required trusted systems, and assign an owner and deadline for replacement. Preserve evidence before disruptive changes.

Open the authoritative advisory

Last verified: 2026-09-22 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeKarel Electronics KarelIPS through build/date identifier 22092026
AdvisoryTR-26-1146
CVECVE-2026-12718
Public disclosure (TR-CERT CNA)2026-09-22 13:47:00 UTC
Recorded CVE timestamp (historical snapshot)2026-09-22 13:51:45.353 UTC
Affected versionsKarelIPS through the authority-listed 22092026 identifier; TR-CERT states that the vendor confirmed the product is unsupported.
Fixed versionNo supported fixed release is available; isolate and retire the unsupported product, following TR-CERT and vendor guidance
CVSS base score9.8 (CVSS v3.1)
CVSS severityCritical
Exploitation statusNot stated by the authority; no exploitation claim is inferred.

What Changed

The reported SQL-injection flaw allows unauthenticated network access to a vulnerable query path. TR-CERT classifies it as blind SQL injection but does not identify the endpoint or a safe patched build. The authority's 22092026 value is a custom version boundary, not evidence of a supported successor.

What To Validate Now

  1. Inventory. Locate Karel Electronics KarelIPS through build/date identifier 22092026 deployments, versions, enabled features, exposure paths, owners, and dependent services.
  2. Establish applicability. Compare each deployment with the authority's affected-version statement: KarelIPS through the authority-listed 22092026 identifier; TR-CERT states that the vendor confirmed the product is unsupported. Do not infer applicability from product family or severity alone.
  3. Remediate. Coordinate isolation and retirement with the application/database owners. Preserve required records and test migration and recovery. No supported fixed release is established by the advisory; do not invent one or treat filtering as equivalent to a vendor fix.
  4. Validate. Verify the intended access restrictions from authorized network locations and confirm essential dependencies before retirement. Document residual reachability, migration status and any time-limited exception.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

The product is unsupported. Compensating controls reduce exposure but do not repair the SQL-injection defect. Avoid exploit testing against production data, and do not infer prior compromise solely from the Critical score.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.