Skip to content

deps: pin oauthlib>=4.0.0 (CVE-2026-49264, CVE-2026-49265) - #2721

Merged
kubernetes-prow[bot] merged 1 commit into
kubernetes-client:masterfrom
friedrichwilken:bump-oauthlib-4
Oct 10, 2026
Merged

kubernetes-prow[bot] merged 1 commit into
kubernetes-client:masterfrom
friedrichwilken:bump-oauthlib-4

Conversation

@friedrichwilken

Copy link
Copy Markdown
Contributor

Fixes #2720.

Two CVEs affect oauthlib 3.x:

  • CVE-2026-49265 -- Timing attack in PKCE code_verifier comparison (CWE-208)
  • CVE-2026-49264 -- Unsafe JSONP callback injection in RevocationEndpoint

The chain is kubernetes → requests-oauthlib → oauthlib>=3.0.0. Since requests-oauthlib only requires >=3.0.0, resolvers can land on the vulnerable 3.x line without a tighter constraint here.

The upstream fix is requests/requests-oauthlib#577 (bump their own lower bound to >=4.0.0), but that project is slow-moving. This PR adds the same protective direct pin used in #2016, following the same pattern that #2434 later cleaned up once the underlying issue was resolved.

The pin can be removed once requests-oauthlib ships a release with oauthlib>=4.0.0 in its own requirements.

@kubernetes-prow kubernetes-prow Bot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Oct 1, 2026
@kubernetes-prow

Copy link
Copy Markdown
Contributor

Welcome @friedrichwilken!

It looks like this is your first PR to kubernetes-client/python 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-client/python has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@kubernetes-prow kubernetes-prow Bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Oct 1, 2026
@kubernetes-prow
kubernetes-prow Bot requested review from roycaihw and yliaog October 1, 2026 15:09
@yliaog

yliaog commented Oct 10, 2026

Copy link
Copy Markdown
Contributor

/lgtm
/approve
/release-note-none

@kubernetes-prow kubernetes-prow Bot added the release-note-none Denotes a PR that doesn't merit a release note. label Oct 10, 2026
@kubernetes-prow kubernetes-prow Bot added lgtm "Looks good to me", indicates that a PR is ready to be merged. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Oct 10, 2026
@kubernetes-prow

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: friedrichwilken, yliaog

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubernetes-prow kubernetes-prow Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 10, 2026
@kubernetes-prow
kubernetes-prow Bot merged commit d680073 into kubernetes-client:master Oct 10, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. release-note-none Denotes a PR that doesn't merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Security: pin oauthlib>=4.0.0 (CVE-2026-49264, CVE-2026-49265)

2 participants