NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

GoBGP does not properly check the input lengthGHSA-hqhq-hp5x-xp3w

MEDIUMFix: osrg/gobgp@5153baf

GHSA-hqhq-hp5x-xp3w is a medium-severity (CVSS 4.3) CWE-1284 vulnerability in github.com/osrg/gobgp. A fix is available for github.com/osrg/gobgp — see the affected versions and patch details below.

Also known asCVE-2025-43970GO-2025-3630
Published
Updated
Affected
2 pkgs
Patched
1 / 2
Exploits
None indexed
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-hqhq-hp5x-xp3w.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk
0.00%0.31%0.62%0.93%0.1%0.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🐹github.com/osrg/gobgp🐹github.com/osrg/gobgp/v3

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

An issue was discovered in GoBGP before 3.35.0. pkg/packet/mrt/mrt.go does not properly check the input length, e.g., by ensuring that there are 12 bytes or 36 bytes (depending on the address family).

Affected Packages

2 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/osrg/gobgpall versionsNo fix
🐹Gogithub.com/osrg/gobgp/v3all versions3.35.0go get github.com/osrg/gobgp/v3@v3.35.0

Affected Products

1 product · 1 configurations
Application
gobgposrg
< 3.35.0
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/osrg/gobgp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    A fix is available for GHSA-hqhq-hp5x-xp3w; check the affected-versions list above or the advisory for the patched release of github.com/osrg/gobgp, then make sure no transitive dependency still pins the vulnerable range.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

An issue was discovered in GoBGP before 3.35.0. pkg/packet/mrt/mrt.go does not properly check the input length, e.g., by ensuring that there are 12 bytes or 36 bytes (depending on the address family).
O3 Security · Impact-Aware SCA

Is GHSA-hqhq-hp5x-xp3w in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
GoBGP does not properly check the input length