# SUSE-SU-2025:20255-1: Security update for python-requests

> An attacker can bypass SSL certificate verification in python-requests if verify=False is set, allowing man-in-the-middle attacks.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Mar 2025

## What is SUSE-SU-2025:20255-1?

SUSE-SU-2025:20255-1 is a vulnerability in python-requests, published on 28 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This update for python-requests fixes the following issues:

- Add patch to inject the default CA bundles if they are not specified.
    (bsc#1226321, bsc#1231500)

- Remove Requires on python-py. 

- update to 2.32.3:
  * Fixed bug breaking the ability to specify custom SSLContexts
    in sub-classes of HTTPAdapter.
  * Fixed issue where Requests started failing to run on Python
    versions compiled without the `ssl` module.

  * To provide a more stable migration for custom HTTPAdapters impacted by the CVE changes in 2.32.0,
    we've renamed _get_connection to a new public API, get_connection_with_tls_context. Existing
    custom HTTPAdapters will need to migrate their code to use this new API. get_connection is
  * Fixed an issue where setting verify=False on the first request from a Session
    will cause subsequent requests to the same origin to also ignore cert verification,
  * verify=True now reuses a global SSLContext which should improve request time
  * Requests now supports optional use of character detection (chardet or charset_normalizer)
    when repackaged or vendored. This enables pip and other projects to minimize their

## Which versions are affected by SUSE-SU-2025:20255-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `python-requests` | SUSE:Linux Micro 6.1 | All versions | 2.32.3-slfo.1.1_2.1 |

## How do I fix SUSE-SU-2025:20255-1?

Upgrade to a fixed version.

## Is SUSE-SU-2025:20255-1 being exploited?

There is no known exploitation of SUSE-SU-2025:20255-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2025:20255-1 and fix it if it is affected.

What it is: SUSE-SU-2025:20255-1 is a vulnerability in python-requests, published on 28 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2025:20255-1 in the wild and no public exploit code.

Affected product: python-requests. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/SUSE-SU-2025-20255-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2025-20255-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2025:20255-1

---
From sbomify Insights: https://insights.sbomify.com/SUSE-SU-2025-20255-1/
Summaries are generated and may contain mistakes; the official description above is the record.