Uses vulnerable version 2.7.1 of libexpat

Open Beginner friendly
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
zig

Research direction

Open build.zig.zon at lines 3-7 and inspect how libexpat 2.7.1 is pinned. Run the supplied git diff command against the Expat release tags to review the listed CVEs and identify an appropriate newer release. Done means the bundle no longer uses 2.7.1 and points to a reviewed release with the vulnerable changes addressed.

Written by the indexing model from the issue text.

Description

Hi!

I found a vulnerable outdated bundle of libexpat 2.7.1 in here at…

https://github.com/allyourcodebase/libexpat/blob/892b8b923bb1cf2983fe2f72fb4648c74a9918cd/build.zig.zon#L3-L7

Based on a quick…

# git diff R_2_7_1 R_2_8_4 -- Changes | grep '^+' | grep -o 'CVE-[0-9-]\+' | sed 's,^,- ,' | sort -u

…I believe the list of unfixed CVEs is this, if you'd like to have a closer look:

  • CVE-2024-8176
  • CVE-2025-59375
  • CVE-2026-24515
  • CVE-2026-25210
  • CVE-2026-32776
  • CVE-2026-32777
  • CVE-2026-32778
  • CVE-2026-41080
  • CVE-2026-45186
  • CVE-2026-50219
  • CVE-2026-56131
  • CVE-2026-56132
  • CVE-2026-56403
  • CVE-2026-56404
  • CVE-2026-56405
  • CVE-2026-56406
  • CVE-2026-56407
  • CVE-2026-56408
  • CVE-2026-56409
  • CVE-2026-56410
  • CVE-2026-56411
  • CVE-2026-56412
  • CVE-2026-66046
  • CVE-2026-72522
  • CVE-2026-76641
  • CVE-2026-76956
  • CVE-2026-76957

Are you aware of this issue?

Best, Sebastian

PS: The next release of Expat is likely upcoming next week.

Dominant language
Zig
Stars
3
Forks
1
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.