Remediate CVE-2026-54297 (faraday) - #145
Open
eng-cve-remediation-app[bot] wants to merge 1 commit into
Open
Conversation
eng-cve-remediation-app
Bot
requested review from
a team and
bastelfreak
as code owners
August 6, 2026 12:37
eng-cve-remediation-app
Bot
force-pushed
the
whitesource-remediate/faraday_faraday
branch
4 times, most recently
from
August 6, 2026 14:11
380b44b to
f221c13
Compare
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
eng-cve-remediation-app
Bot
force-pushed
the
whitesource-remediate/faraday_faraday
branch
from
August 6, 2026 14:29
f221c13 to
f3a0afe
Compare
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
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.
This PR contains the following updates:
unknown→2.14.3By merging this PR, the below vulnerabilities will be automatically resolved:
Bump strategy
faraday CVE-2026-54297 fix
faradayis a direct runtime dependency, declared inpuppet_forge.gemspec(this repo has no gem pins in
Gemfile— it just doesgemspec, so thegemspec is the manifest for runtime deps).
spec.add_runtime_dependency "faraday", "~> 2.0". Thistechnically permitted 2.14.3, but set no floor — Bundler could just as
easily have resolved to an older, vulnerable 2.x release.
Gemfile.lockis gitignored in this repo, so a lockfile that happens to show 2.14.3
today is not durable; the next resolve (Mend's scan, CI, this bot) could
land back on a vulnerable version with no code change.
>= 2.14.3", "< 3.0"— enforces the fix as a floor whilepreserving the original "stay on faraday 2.x" intent.
bundle lock; regeneratedGemfile.locknow resolvesfaradayto2.14.3.bundle checkpasses.faraday-follow_redirectsandfaraday-net_httpare versionedindependently of
faraday(not pinned at the same current version), sothey were left untouched.