Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
#2,720 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 3 天内回复

@friedrichwilken 已经在做这个了。

开始于 2026年10月1日。

  • #2721 来自 @friedrichwilken —— 未关闭

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
30/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
python
领域
security

调研方向

Start with requirements.txt and compare the requested dependency pin with the protective pattern from #2016. Add the direct oauthlib>=4.0.0 constraint, then verify that the dependency resolves to the fixed 4.0.0 line; the issue notes that this pin can later be removed after requests-oauthlib ships its raised lower bound.

由索引模型根据 Issue 内容生成。

描述

Two CVEs were published against oauthlib affecting all 3.x releases:

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

Both are fixed in oauthlib 4.0.0.

The dependency chain here is:

kubernetes → requests-oauthlib → oauthlib>=3.0.0

requests-oauthlib declares oauthlib>=3.0.0, which allows resolvers to land on the vulnerable 3.x line. The upstream fix is requests/requests-oauthlib#577, but that project is slow-moving.

The same protective pattern was used before in #2016 -- adding a direct oauthlib pin to requirements.txt. A PR with the one-line fix is attached.

Once requests/requests-oauthlib#577 merges and a new requests-oauthlib release ships with the raised lower bound, this pin can be removed (same as #2434 cleaned up the previous one).

主要语言
Python
星标
7.7k
派生
3.5k
平均合并
3 天 4 小时
30 天内合并 PR
9

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

kubernetes-client/python 的其他 Issue

查看 kubernetes-client/python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。