How severe is CVE-2026-89197?

CVE-2026-89197 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-89197?

Affected package information for CVE-2026-89197 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2026-89197?

No fixed release is recorded for CVE-2026-89197 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2026-89197 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2026-89197 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2026-89197 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-89197 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is CVE-2026-89197?

CVE-2026-89197 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-89197 published, and has it been updated?

CVE-2026-89197 was published on October 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

Not in CISA KEV

HIGH severity

CVE-2026-89197

HIGH

CVE-2026-89197 is a high-severity (CVSS 8.8) SQL Injection vulnerability. No vendor fix is recorded yet; mitigation options are listed below.

A vulnerability has been identified in RUGGEDCOM CROSSBOW (All versions < V6.0). Affected devices do not properly validate or sanitize input in the Value field of notification conditions…

Published

Oct 13, 2026

Updated

Oct 13, 2026

Affected

—

Patched

—

Exploits

None indexed

Exploitation data as of Oct 13, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Description

A vulnerability has been identified in RUGGEDCOM CROSSBOW (All versions < V6.0). Affected devices do not properly validate or sanitize input in the Value field of notification conditions processed during the Notification Profile configuration. This could allow an authenticated attacker with specific privileges to execute arbitrary SQL commands on the underlying database.

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2026-89197 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-89197 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2026-89197

Description

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Frequently Asked Questions

Is CVE-2026-89197 in your dependencies?