cve.bz

CVE-2026-7734 osrg gobgp: Improper Resource Shutdown or Release

6.9 mediumEPSS 0.5%Fix available

Medium (6.9) in osrg gobgp. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/osrg/gobgp/v4 4.4.0.

On this page
A vulnerability has been found in osrg GoBGP up to 4.3.0. This impacts the function SRv6L3ServiceAttribute.DecodeFromBytes of the file pkg/packet/bgp/prefix_sid.go of the component SRv6 L3 Service. Such manipulation of the argument data leads to denial of service. The attack may be performed from remote. Upgrading to version 4.4.0 will fix this issue. The name of the patch is f9f7b55ec258e514be0264871fa645a2c3edad11. You should upgrade the affected component.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 41st percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-05-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-404 Improper Resource Shutdown or Release
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-7734 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-7734?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-7734?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-7734 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-7734

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-7734](https://cve.bz/cve/badge/CVE-2026-7734.svg)](https://cve.bz/cve/CVE-2026-7734)

HTML:

<a href="https://cve.bz/cve/CVE-2026-7734"><img src="https://cve.bz/cve/badge/CVE-2026-7734.svg" alt="CVE-2026-7734"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
osrg:gobgpbefore 4.4.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-vm3g-8xwv-mxfpGogithub.com/osrg/gobgp/v4<4.4.04.4.0
GO-2026-5665Gogithub.com/osrg/gobgp/v4<4.4.04.4.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13gobgpno fix listedDEBIAN-CVE-2026-7734
Debian14gobgp4.4.0-1DEBIAN-CVE-2026-7734
Ubuntu25.10gobgpno fix listedUBUNTU-CVE-2026-7734
UbuntuPro:18.04:LTSgobgp1.29-1ubuntu0.1+esm2USN-8348-1
UbuntuPro:20.04:LTSgobgp2.12.0-1ubuntu0.1~esm3USN-8348-1
UbuntuPro:22.04:LTSgobgp2.25.0-3ubuntu0.1+esm4UBUNTU-CVE-2026-7734 USN-8348-1
UbuntuPro:24.04:LTSgobgp3.23.0-1ubuntu0.3+esm4UBUNTU-CVE-2026-7734 USN-8348-1
UbuntuPro:26.04:LTSgobgp3.36.0-2ubuntu0.1~esm1UBUNTU-CVE-2026-7734 USN-8348-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Attack patterns (CAPEC)

  • CAPEC-125 Flooding Likelihood: High · Severity: Medium
  • CAPEC-130 Excessive Allocation Likelihood: Medium · Severity: Medium
  • CAPEC-131 Resource Leak Exposure Likelihood: Medium · Severity: Medium
  • CAPEC-494 TCP Fragmentation
  • CAPEC-495 UDP Fragmentation
  • CAPEC-496 ICMP Fragmentation
  • CAPEC-666 BlueSmacking Likelihood: Medium · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON