bird-lg-go: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') and Exposure of Sensitive Information to an…
bird-lg-go v1.4.6 and earlier are affected when the bird-lgproxy /traceroute endpoint is reachable and receives unsanitized input. The issue is fixed in 1.4.7. No vendor rating is given.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.4.7
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.4.7.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
bird-lg-go, a BIRD looking glass written in Go, contains a flaw in how it handles input paths that lets a remote attacker read arbitrary local files without logging in, including sensitive ones such as /etc/shadow. The problem is fixed in version 1.4.7.
Read the original description
bird-lg-go is a BIRD looking glass in Go. Prior to version 1.4.7, unsanitized input path enables arbitrary local file read, allowing an unauthenticated remote attacker to read sensitive files such as /etc/shadow and /root/.bash_history. This issue has been patched in version 1.4.7.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.4.7.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- xddxdd bird-lg-go
fixed in 1.4.7
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-63644
Is CVE-2026-63644 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The /traceroute endpoint passes unsanitized input into a command, so crafted input can be interpreted as command arguments. The advisory says this allows reading local files on the server, such as /etc/shadow and /root/.bash_history.Source: github.com
Which versions are affected by CVE-2026-63644?
bird-lg-go: before 1.4.7.Source: cve.now feed data
Am I affected, and how do I check?
The advisory says versions v1.4.6 and earlier are affected, and that the issue remained unfixed through v1.4.5. The relevant setup is a reachable bird-lgproxy /traceroute endpoint, so check the bird-lg-go version in use and whether that endpoint is exposed.Source: github.com
How do I fix CVE-2026-63644?
Upgrade bird-lg-go to 1.4.7, the version the advisory says properly addresses the issue.Source: github.com