# CVE-2026-4433: Misconfiguration in Tenable Operation Technology

> Misconfigured SSH settings in Tenable OT allow attackers to exfiltrate system information, potentially aiding further compromise.

- **Severity:** Low 1.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Mar 2026
- **Updated:** 25 Mar 2026
- **Also known as:** GHSA-r3v4-cfx9-jmvv

## What is CVE-2026-4433?

CVE-2026-4433 is a low-severity vulnerability in Tenable, Inc. Tenable Operation Technology, published on 24 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

An SSH misconfigurations exists in Tenable OT that led to the potential exfiltration of socket, port, and service information via the ostunnel user and GatewayPorts. This could be used to potentially glean information about the underlying system and give an attacker information that could be used to attempt to compromise the host.

Weakness: CWE-16

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

It affects 1 product.


Products: Tenable Operational Technology Exposure.

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

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

## Is CVE-2026-4433 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4433 is a low-severity vulnerability in Tenable, Inc. Tenable Operation Technology, published on 24 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-4433 in the wild and no public exploit code.

Affected product: Tenable, Inc. Tenable Operation Technology. 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-4433/ (Markdown: https://insights.sbomify.com/CVE-2026-4433/index.md)
```

## Sources

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

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