CVE-2026-111943VulnerabilityPublished 24 Oct 2026Updated 26 Oct 2026

SUSE · istioctl-1.31.3-1.1 on GA media

Affects SUSESource GCVE Database

Authoritative record:CVE-2026-111943· Medium

Not known to be exploited : upgrade SUSE x509 to 1.27.3 or 1.26.10 when convenient.

Data as of 26 Oct 2026, 17:16 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.27.3, 1.26.10

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade crypto/x509 to 1.27.3 or 1.26.10.

Affected software

Product	Affected	Fixed in
Go standard librarycrypto/x509	Affected >=1.27.0-0 <1.27.3	Fixed in 1.27.3
Go standard librarycrypto/x509	Affected <1.26.10	Fixed in 1.26.10
Gocrypto/x509`pkg:golang/crypto/x509`Other threats	Affected <1.26.10 >=1.27.0-0 <1.27.3	Fixed in 1.26.10 1.27.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

These are all security issues fixed in the istioctl-1.31.3-1.1 package on the GA media of openSUSE Tumbleweed.

References

Community reviews

Loading reviews…