Update dependency requests to v2.33.0 [SECURITY]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
requests (changelog)	2.32.5 → 2.33.0

---

Requests has Insecure Temp File Reuse in its extract_zipped_paths() utility function

CVE-2026-25645 / GHSA-gc5v-m9x4-r6x2

More information

Details

Impact

The requests.utils.extract_zipped_paths() utility function uses a predictable filename when extracting files from zip archives into the system temporary directory. If the target file already exists, it is reused without validation. A local attacker with write access to the temp directory could pre-create a malicious file that would be loaded in place of the legitimate one.

Affected usages

Standard usage of the Requests library is not affected by this vulnerability. Only applications that call extract_zipped_paths() directly are impacted.

Remediation

Upgrade to at least Requests 2.33.0, where the library now extracts files to a non-deterministic location.

If developers are unable to upgrade, they can set TMPDIR in their environment to a directory with restricted write access.

Severity

• CVSS Score: 4.4 / 10 (Medium)
• Vector String: CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N

References

• https://github.com/psf/requests/security/advisories/GHSA-gc5v-m9x4-r6x2
• https://github.com/psf/requests/commit/66d21cb07bd6255b1280291c4fafb71803cdb3b7
• https://github.com/psf/requests/releases/tag/v2.33.0
• https://nvd.nist.gov/vuln/detail/CVE-2026-25645
• https://github.com/advisories/GHSA-gc5v-m9x4-r6x2

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

psf/requests (requests)

v2.33.0

Compare Source

Announcements

• 📣 Requests is adding inline types. If you have a typed code base that
  uses Requests, please take a look at #​7271. Give it a try, and report
  any gaps or feedback you may have in the issue. 📣

Security

• CVE-2026-25645 requests.utils.extract_zipped_paths now extracts
  contents to a non-deterministic location to prevent malicious file
  replacement. This does not affect default usage of Requests, only
  applications calling the utility function directly.

Improvements

• Migrated to a PEP 517 build system using setuptools. (#​7012)

Bugfixes

• Fixed an issue where an empty netrc entry could cause
  malformed authentication to be applied to Requests on
  Python 3.11+. (#​7205)

Deprecations

• Dropped support for Python 3.9 following its end of support. (#​7196)

Documentation

• Various typo fixes and doc improvements.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

The automated inspectors have returned with their findings. 🕵️‍♂️

I've aggregated the results of the automated checks for this PR below.

📋 Repo Health

Ensuring the repo is getting enough sleep (aka stable releases). 💤

✅ All required files present.

Latest Version: 0.13.9a2

✅ ovos_utils/version.py — Version file
✅ README.md — README
✅ LICENSE — License file
✅ pyproject.toml — pyproject.toml
⚠️ setup.py — setup.py
✅ CHANGELOG.md — Changelog
✅ ovos_utils/version.py has valid version block markers

🔒 Security (pip-audit)

Ensuring our project remains safe and secure. 🛡️

✅ No known vulnerabilities found (47 packages scanned).

🔍 Lint

I've finished the digital walk-through of your PR. 🚶‍♂️

❌ ruff: issues found — see job log

📊 Coverage

A forensic analysis of your test coverage. 🔍

✅ 85.2% total coverage

Files below 80% coverage (5 files)

File	Coverage	Missing lines
ovos_utils/log_parser.py	48.4%	225
ovos_utils/__init__.py	63.6%	16
ovos_utils/file_utils.py	74.4%	56
ovos_utils/thread_utils.py	76.9%	12
ovos_utils/geolocation.py	78.4%	22

Full report: download the coverage-report artifact.

🏷️ Release Preview

A detailed preview of the next release cycle. 🎬

Current: 0.13.9a2 → Next: 0.13.9a3

Signal	Value
Label	ignore-for-release
PR title	Update dependency requests to v2.33.0 [SECURITY]
Bump	alpha

⚠️ No conventional commit prefix — alpha-only bump.
Suggested: fix: update the thing or feat: update the thing

---

🚀 Release Channel Compatibility

Predicted next version: 0.13.9a3

Channel	Status	Note	Current Constraint
Stable	❌	Too new (must be <0.9.0)	ovos-utils>=0.8.1,<0.9.0
Testing	❌	Too new (must be <0.8.5)	ovos-utils>=0.8.4,<0.8.5
Alpha	✅	Compatible	ovos-utils>=0.13.9a2

🔨 Build Tests

Checking the blueprint against the actual construction. 📐

✅ All versions pass

Python	Build	Install	Tests
3.10	✅	✅	✅
3.11	✅	✅	✅
3.12	✅	✅	✅
3.13	✅	✅	✅
3.14	✅	✅	✅

⚖️ License Check

I've checked the licenses of all dev-dependencies too. 🛠️

✅ No license violations found.

Policy: Apache 2.0 (universal donor). StrongCopyleft / NetworkCopyleft / WeakCopyleft / Other / Error categories fail. MPL allowed.

---

Your automated guardian for repository health 🛡️

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: uv.lock

Command failed: uv lock --upgrade-package requests
Using CPython 3.14.6 interpreter at: /opt/containerbase/tools/python/3.14.6/bin/python3
  × No solution found when resolving dependencies for split (markers:
  │ python_full_version == '3.9.*'):
  ╰─▶ Because the requested Python version (>=3.9) does not satisfy
      Python>=3.10 and ovos-spec-tools>=0.16.1a2 depends on Python>=3.10, we
      can conclude that ovos-spec-tools>=0.16.1a2 cannot be used.
      And because only the following versions of ovos-spec-tools are
      available:
          ovos-spec-tools<=0.16.1a2
          ovos-spec-tools==0.17.1a1
          ovos-spec-tools==0.17.2a1
          ovos-spec-tools==0.17.3a1
          ovos-spec-tools==0.18.0a1
          ovos-spec-tools==1.0.0a1
          ovos-spec-tools==1.1.0a1
          ovos-spec-tools==1.2.0a1
          ovos-spec-tools==1.2.1a1
          ovos-spec-tools==1.2.2a1
          ovos-spec-tools==1.2.3a1
          ovos-spec-tools==1.3.0a1
          ovos-spec-tools==1.4.0a1
          ovos-spec-tools==1.4.1a1
          ovos-spec-tools==1.5.0a1
          ovos-spec-tools==1.5.1a1
          ovos-spec-tools==1.5.1a2
      we can conclude that ovos-spec-tools>=0.16.1a2 cannot be used.
      And because your project depends on ovos-spec-tools>=0.16.1a2 and your
      project requires ovos-utils[extras], we can conclude that your project's
      requirements are unsatisfiable.

hint: While the active Python version is 3.14, the resolution failed for other Python versions supported by your project. Consider limiting your project's supported Python versions using `requires-python`.
hint: The `requires-python` value (>=3.9) includes Python versions that are not supported by your dependencies (e.g., ovos-spec-tools>=0.16.1a2 only supports >=3.10). Consider using a more restrictive `requires-python` value (like >=3.10).

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.