CVE-2026-45047
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedbird-lg-go is a BIRD looking glass in Go. Prior to 1.4.5, the apiHandler (and similarly webHandlerTelegramBot) processes user-provided JSON payloads by directly using json.NewDecoder(r.Body).Decode(&request) without restricting the maximum read size. An unauthenticated remote attacker can stream an extremely large, endless JSON payload (e.g., several Gigabytes of padding) over a single TCP connection. Because Go's JSON decoder attempts to allocate memory for the entire parsed structure, this rapidly exhausts the host's physical RAM or container limits, leading to an unrecoverable fatal error: runtime: out of memory. This vulnerability is fixed in 1.4.5.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn bird-lg-go versions prior to 1.4.5, the apiHandler processes JSON payloads without limiting maximum read size. An unauthenticated attacker can stream gigabytes of JSON data over a single TCP connection, causing Go's json.NewDecoder to attempt allocating memory for the entire payload, exhausting host RAM and triggering a fatal OOM error.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed bird-lg-go versionRun 'bird-lg-go --version' or check the binary version via 'ls -la' and compare to the affected range (versions prior to 1.4.5)Affected if Version is below 1.4.5
-
Verify apiHandler is enabledInspect the bird-lg-go configuration file (typically /etc/bird-lg-lg.conf or similar) and search for apiHandler or API-related settings; also check if the binary was started with API-enabling flagsAffected if apiHandler or API endpoint configuration is present and enabled
-
Confirm network exposure of API serviceReview firewall rules, service binding configuration (check if listening on 0.0.0.0 vs 127.0.0.1), and network access controls; use 'netstat -tlnp' or 'ss -tlnp' to see which interfaces the service binds toAffected if The API service is reachable from untrusted network segments or the internet
Environment is affected if running bird-lg-go version prior to 1.4.5 with the apiHandler enabled and exposed to network access, allowing unauthenticated attackers to trigger memory exhaustion via large JSON payloads.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to bird-lg-go version 1.4.5 or later, which implements a maximum read size limit on JSON payloads to prevent memory exhaustion attacks.
1.4.5
- Identify the current version of bird-lg-go currently running
- Upgrade bird-lg-go to version 1.4.5 or later using your deployment method (e.g., package manager, binary replacement, or container update)
- Restart the bird-lg-go service to load the new version
- Verify the service is running the fixed version (1.4.5 or later)
- Test that the API endpoint still functions normally with legitimate JSON requests
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45047 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45047 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data