Skip to main content
VulnerabilityPublished Updated

CVE-2026-81515: SteeltoeOSS security-advisories · Improper Handling of Exceptional Conditions

Affects SteeltoeOSS security-advisoriesSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 4.3.0 soon.

Data as of 1 Nov 2026, 22:58 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.3.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 1 Nov 2026.

What to do

Upgrade security-advisories and steeltoeoss/Steeltoe to 4.3.0.

Affected software

ProductAffectedFixed in
SteeltoeOSSsecurity-advisoriesAffected
  • >=4.0.0 <4.3.0
Fixed in
  • 4.3.0
GitHubsteeltoeoss/Steeltoepkg:github/steeltoeoss/SteeltoeOther threatsAffected
  • >=4.0.0 <4.3.0
Fixed in
  • 4.3.0

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

AI-suggested

This vulnerability is fixed in SteeltoeOSS version 4.3.0. Users should upgrade to version 4.3.0 or later to remediate the issue. No other mitigation or temporary workaround is indicated.

Description

Steeltoe is an open source project that provides a collection of libraries that helps users build cloud-native applications. From 4.0.0 until 4.3.0, EurekaDiscoveryClient deserializes the registry response as one unit, and an unrecognized actionType or status, a non-Boolean isCoordinatingDiscoveryServer, or a nonnumeric timestamp can abort the entire response. A principal that can register or update an instance can cause all connected Steeltoe clients to receive an empty or stale instance list until the malformed registration is removed. The JsonInstanceInfoConverter, BoolStringJsonConverter, and LongStringJsonConverter parsing paths are affected. This issue is distinct from the earlier DataCenterInfo.name parsing vulnerability. This issue is fixed in version 4.3.0.

References

Community reviews

Loading reviews…