Correct arrow CVE-2026-25087 suppression rationale (false positive) - #724
Merged
fintrac-alex-hewson merged 2 commits intoJul 20, 2026
Merged
Conversation
…ot no-fix) CVE-2026-25087 is a use-after-free in the Apache Arrow C++ IPC reader (fixed in Arrow C++ 23.0.1). TRAC depends only on pure-Java arrow modules (arrow-vector, arrow-memory-*, arrow-format, arrow-algorithm) with no JNI/C++-bundling modules, so the vulnerable code is not present - a false positive, not an unfixed vuln. The suppression is kept (it actively matches our arrow 18.3.0 via the CVE CPE), but a version bump cannot clear it: arrow-java is now versioned independently of Arrow C++ (latest arrow-java is 19.0.0), and the CVE CPE range (15.0.0-23.0.0) covers all current arrow-java versions. Only the comment changes.
fintrac-alex-hewson
temporarily deployed
to
integration
July 20, 2026 17:31 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
fintrac-alex-hewson
temporarily deployed
to
integration
July 20, 2026 17:31 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
fintrac-alex-hewson
temporarily deployed
to
integration
July 20, 2026 17:31 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
fintrac-alex-hewson
temporarily deployed
to
integration
July 20, 2026 17:31 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
fintrac-alex-hewson
temporarily deployed
to
integration
July 20, 2026 17:31 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
fintrac-alex-hewson
temporarily deployed
to
integration
July 20, 2026 17:31 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
fintrac-alex-hewson
temporarily deployed
to
integration
July 20, 2026 20:38 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
fintrac-alex-hewson
temporarily deployed
to
integration
July 20, 2026 20:38 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
fintrac-alex-hewson
temporarily deployed
to
integration
July 20, 2026 20:38 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
fintrac-alex-hewson
temporarily deployed
to
integration
July 20, 2026 20:38 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
fintrac-alex-hewson
temporarily deployed
to
integration
July 20, 2026 20:38 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
fintrac-alex-hewson
temporarily deployed
to
integration
July 20, 2026 20:38 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
fintrac-alex-hewson
deleted the
fix/arrow-cve-2026-25087-suppression-reason
branch
July 20, 2026 20:58
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Corrects the rationale on the Apache Arrow CVE-2026-25087 suppression. Comment-only change — the suppression itself is kept.
Why
The suppression said "no fix available at time of writing", which is misleading. In fact it's a false positive against the Java library:
arrow-vector,arrow-memory-core/netty(-buffer-patch),arrow-format,arrow-algorithm— with no JNI/C++-bundling modules (arrow-dataset/gandiva/c-data/orc). The vulnerable C++ code isn't present, so we're not exposed (confirmed against the resolved dependency set).Why keep the suppression (no version bump)
The entry actively matches our arrow 18.3.0 via the CVE's CPE, so removing it would turn
platform_compliancered. And a bump can't clear it: arrow-java is now versioned independently of Arrow C++ (latest arrow-java on Maven Central is 19.0.0 — there is no arrow-java 23.0.1), and the CVE's CPE range15.0.0–23.0.0still covers all current arrow-java versions.Updating Arrow itself is tracked separately as future work (it's a large jump, and Arrow is heavily used in the data codecs).
Change
dev/compliance/owasp-false-positives.xml— replace the CVE-2026-25087 comment; suppression unchanged.Test plan
platform_compliancestill passes (suppression unchanged; only the comment differs)