<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 02:32:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-42285 — GoBGP: Panic in AdjRib.Update via malformed BGP Update message (Nil Pointer Dereference)</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-42285</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; osrg gobgp&lt;/p&gt;
&lt;p&gt;GoBGP is an open source Border Gateway Protocol (BGP) implementation in the Go Programming Language. In version 4.4.0, an unauthenticated remote BGP peer can trigger a fatal panic in GoBGP by sending a specially crafted BGP UPDATE message. When the server receives a message with inconsistent attribute lengths, it improperly handles the internal state transition to a &amp;#34;withdraw&amp;#34; action, leading to a nil pointer dereference in the AdjRib.Update function. This causes the entire GoBGP process to crash, resulting in a complete loss of service availability. This issue has been patched in version 4.5.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; osrg gobgp&lt;/p&gt;
&lt;p&gt;GoBGP is an open source Border Gateway Protocol (BGP) implementation in the Go Programming Language. In version 4.4.0, an unauthenticated remote BGP peer can trigger a fatal panic in GoBGP by sending a specially crafted BGP UPDATE message. When the server receives a message with inconsistent attribute lengths, it improperly handles the internal state transition to a &amp;#34;withdraw&amp;#34; action, leading to a nil pointer dereference in the AdjRib.Update function. This causes the entire GoBGP process to crash, resulting in a complete loss of service availability. This issue has been patched in version 4.5.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-42285</guid>
    </item>
    <item>
      <title>GHSA-p3w2-64xm-833j — GoBGP has a panic in AdjRib.Update via malformed BGP Update message (Nil Pointer Dereference)</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-p3w2-64xm-833j</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/osrg/gobgp/v4&lt;/p&gt;
&lt;p&gt;### Summary
Remote Denial of Service (DoS) via Nil Pointer Dereference in BGP Update Processing
An unauthenticated remote BGP peer can trigger a fatal panic in GoBGP by sending a specially crafted BGP UPDATE message. When the server receives a message with inconsistent attribute lengths, it improperly handles the internal state transition to a &amp;#34;withdraw&amp;#34; action, leading to a nil pointer dereference in the AdjRib.Update function. This causes the entire GoBGP process to crash, resulting in a complete loss of service availability.&lt;/p&gt;
&lt;p&gt;### Details
The vulnerability originates in the interaction between the BGP message decoding logic and the Adj-RIB table management.&lt;/p&gt;
&lt;p&gt;Triggering Condition: When a BGP UPDATE message contains attributes that fail validation (e.g., &amp;#34;attribute value length is short&amp;#34;), GoBGP logs a warning: the received Update message was treated as withdraw.&lt;/p&gt;
&lt;p&gt;Code Path:&lt;/p&gt;
&lt;p&gt;The message reaches github.com/osrg/gobgp/v4/pkg/server.(*peer).handleUpdate.&lt;/p&gt;
&lt;p&gt;Due to the malformed attributes, the message is processed as a withdrawal, but the internal representation of the path or its attributes becomes nil.&lt;/p&gt;
&lt;p&gt;The execution flows to internal/pkg/table/adj.go:127 within (*AdjRib).Update.&lt;/p&gt;
&lt;p&gt;The Flaw: At line 127 in adj.go, the code attempts to access a member of a structure (likely the path or a specific attribute container) that is nil due to the previous validation failure.&lt;/p&gt;
&lt;p&gt;Log Snippet:
```
{&amp;#34;time&amp;#34;:&amp;#34;2026-04-21T12:43:10.009107962+08:00&amp;#34;,&amp;#34;level&amp;#34;:&amp;#34;WARN&amp;#34;,&amp;#34;msg&amp;#34;:&amp;#34;the received Update messa…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/osrg/gobgp/v4&lt;/p&gt;
&lt;p&gt;### Summary
Remote Denial of Service (DoS) via Nil Pointer Dereference in BGP Update Processing
An unauthenticated remote BGP peer can trigger a fatal panic in GoBGP by sending a specially crafted BGP UPDATE message. When the server receives a message with inconsistent attribute lengths, it improperly handles the internal state transition to a &amp;#34;withdraw&amp;#34; action, leading to a nil pointer dereference in the AdjRib.Update function. This causes the entire GoBGP process to crash, resulting in a complete loss of service availability.&lt;/p&gt;
&lt;p&gt;### Details
The vulnerability originates in the interaction between the BGP message decoding logic and the Adj-RIB table management.&lt;/p&gt;
&lt;p&gt;Triggering Condition: When a BGP UPDATE message contains attributes that fail validation (e.g., &amp;#34;attribute value length is short&amp;#34;), GoBGP logs a warning: the received Update message was treated as withdraw.&lt;/p&gt;
&lt;p&gt;Code Path:&lt;/p&gt;
&lt;p&gt;The message reaches github.com/osrg/gobgp/v4/pkg/server.(*peer).handleUpdate.&lt;/p&gt;
&lt;p&gt;Due to the malformed attributes, the message is processed as a withdrawal, but the internal representation of the path or its attributes becomes nil.&lt;/p&gt;
&lt;p&gt;The execution flows to internal/pkg/table/adj.go:127 within (*AdjRib).Update.&lt;/p&gt;
&lt;p&gt;The Flaw: At line 127 in adj.go, the code attempts to access a member of a structure (likely the path or a specific attribute container) that is nil due to the previous validation failure.&lt;/p&gt;
&lt;p&gt;Log Snippet:
```
{&amp;#34;time&amp;#34;:&amp;#34;2026-04-21T12:43:10.009107962+08:00&amp;#34;,&amp;#34;level&amp;#34;:&amp;#34;WARN&amp;#34;,&amp;#34;msg&amp;#34;:&amp;#34;the received Update messa…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-p3w2-64xm-833j</guid>
    </item>
  </channel>
</rss>
