<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T02:25:59.585255+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-81515</id>
    <title>fkie_cve-2026-81515</title>
    <updated>2026-09-30T02:25:59.598222+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-81515"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-hr73-3gpv-hh6q</id>
    <title>GHSA-hr73-3gpv-hh6q — Steeltoe.Discovery.Eureka: malformed enum/bool/timestamp field aborts entire registry fetch (DoS)</title>
    <updated>2026-09-30T02:25:59.598310+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> NuGet: Steeltoe.Discovery.Eureka</p>
<p>## Summary</p>
<p>Steeltoe's Eureka discovery client deserializes the registry response as a single unit. If any registered instance contains a field value that cannot be parsed (for example, an unrecognized `actionType`, a non-boolean value for `isCoordinatingDiscoveryServer`, or a non-numeric timestamp), deserialization of the entire registry fails. All Steeltoe Eureka clients connected to that registry then receive an empty or stale instance list until the malformed registration is removed.</p>
<p>This is a related but distinct issue from [CVE-2026-50196](https://github.com/advisories/GHSA-j8ph-6fxj-g533), which addressed only the `DataCenterInfo.name` field.</p>
<p>## Impact</p>
<p>Any principal that can register or update a service instance in the Eureka registry can trigger a service-discovery outage for all Steeltoe applications connected to the same registry. The outage persists until the offending registration is removed.</p>
<p>## Affected configuration</p>
<p>* Application uses `EurekaDiscoveryClient` (any deployment, including self-hosted Eureka).
* The registry contains at least one service instance with an unrecognized value in a field such as `actionType`, `status`, `isCoordinatingDiscoveryServer`, or timestamp fields.
* Mixed-platform environments — for example, Java or Spring services co-existing in the same Eureka registry — are more likely to encounter this condition.</p>
<p>## Mitigations</p>
<p>If an immediate upgrade is not possible:</p>
<p>* Audit the Eureka registry for registrations containing non-stand…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-hr73-3gpv-hh6q"/>
  </entry>
</feed>
