[CVE-2026-54428] Bump httpclient5 to 5.6.2 - #462
Merged
Jan-Kazlouski-elastic merged 1 commit intoAug 4, 2026
Conversation
Pulls httpcore5/httpcore5-h2 5.4.3, clearing High CVE-2026-54428 and CVE-2026-54399 (HTTP resource exhaustion). Also retains the CVE-2025-8671 fix. Part of elastic/security#13046 Co-authored-by: Cursor <cursoragent@cursor.com>
erikcurrin-elastic
approved these changes
Aug 3, 2026
Jan-Kazlouski-elastic
deleted the
jan-kazlouski/13046-cve-2026-54428-fix
branch
August 4, 2026 07:38
This was referenced Aug 4, 2026
Jan-Kazlouski-elastic
added a commit
that referenced
this pull request
Aug 4, 2026
### Closes #465 Same failure mode as [elastic/connectors#4289](elastic/connectors#4289). The repository's default `GITHUB_TOKEN` permission is now read-only: ```text $ gh api repos/elastic/crawler/actions/permissions/workflow {"default_workflow_permissions":"read","can_approve_pull_request_reviews":true} ``` Neither workflow in `.github/workflows/` declared a `permissions:` block, so they inherit that default. After merging #462, backport failed with: 1. `Permission to elastic/crawler.git denied to github-actions[bot]` on `git push` of the backport branch (`contents: write` missing) 2. `Resource not accessible by integration` when posting the failure comment on the source PR (`pull-requests: write` missing) This declares the scopes each workflow actually needs (least privilege), overriding the read-only default without flipping the repository setting back to read/write for everything. | Workflow | Scopes | Why | |----------|--------|-----| | `add-labels-main.yml` | `contents: read`, `pull-requests: write` | checkout reads `product_version`; action labels the PR | | `backport.yml` | `contents: write`, `pull-requests: write` | pushes cherry-pick branches, opens backport PRs, comments status on the source PR | `backport.yml`'s `approver_token` (`REPO_SCOPED_TOKEN`) is unaffected by the `GITHUB_TOKEN` default. ### Note on verifying this PR `pull_request_target` always runs the workflow from the **base** branch, so backport/add-labels will still use `main`'s copy (without permissions) while this PR is open. The fix takes effect only after merge. After merge, re-trigger backport for any PRs that failed (e.g. #462) by re-adding the `auto-backport` label, or run the manual command from the failure comment. ### Checklists #### Pre-Review Checklist - [x] This PR does NOT contain credentials of any kind - [x] This PR has a meaningful title - [x] This PR links to all relevant GitHub issues - [x] this PR has a thorough description - [ ] Covered the changes with automated tests (no workflow YAML test harness) - [x] Tested the changes locally (YAML structure + permissions blocks verified) - [x] Added a label for each target release version - [ ] Considered corresponding documentation changes Deliberately **not** labelled `auto-backport`: both workflows are gated on `branches: main`, so copies on maintenance branches never run. #### Changes Requiring Extra Attention - [x] Security-related changes — both workflows use `pull_request_target`. Grants are safe: neither checks out or executes PR head code. `add-labels-main.yml` checks out the base ref and only reads `product_version`. `backport.yml` checks out a pinned external actions repo and only runs after merge into `main`. ### Release Note No user-facing change; CI configuration only. Made with [Cursor](https://cursor.com) --------- Co-authored-by: Cursor <cursoragent@cursor.com>
Jan-Kazlouski-elastic
added a commit
that referenced
this pull request
Aug 4, 2026
Backports the following commits to 1.0: - [CVE-2026-54428] Bump httpclient5 to 5.6.2 (#462) Co-authored-by: Jan-Kazlouski-elastic <jan.kazlouski@elastic.co> Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Part of https://github.com/elastic/security/issues/13046
Also covers:
Resolves CVE-2026-54428 (high) — HTTP/2 HPACK decoder resource exhaustion in httpcore5-h2. Bumping
httpclient5to 5.6.2 pullshttpcore5/httpcore5-h25.4.3, which also clears CVE-2026-54399.Changes
Jarfile/Jars.lock/vendor/jars/:httpclient55.5.1→5.6.2;httpcore5/httpcore5-h25.3.6→5.4.3Testing
make test: 690 examples, 0 failuresScanner A/B (
CVE-2026-54428/CVE-2026-54399)Made with Cursor