pycares prior 4.9.0 Channel Object __del__ use after free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.00

Summaryinfo

A vulnerability was found in pycares. It has been rated as critical. Affected by this vulnerability is the function __del__ of the component Channel Object Handler. This manipulation causes use after free. This vulnerability is tracked as CVE-2025-48945. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as critical was found in pycares. Affected by this vulnerability is the function __del__ of the component Channel Object Handler. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability.

The advisory is shared at bugzilla.redhat.com. This vulnerability is known as CVE-2025-48945 since 05/28/2025. The exploitation appears to be easy. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 266018 (SUSE SLED15 / SLES15 / openSUSE 15 Security Update : python-pycares (SUSE-SU-2025:03354-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.9.0 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (266018). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 266018
Nessus Name: SUSE SLED15 / SLES15 / openSUSE 15 Security Update : python-pycares (SUSE-SU-2025:03354-1)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: pycares 4.9.0

Timelineinfo

05/28/2025 CVE reserved
06/17/2025 +20 days Advisory disclosed
06/17/2025 +0 days VulDB entry created
09/27/2025 +102 days VulDB entry last update

Sourcesinfo

Advisory: bugzilla.redhat.com
Status: Confirmed

CVE: CVE-2025-48945 (🔒)
GCVE (CVE): GCVE-0-2025-48945
GCVE (VulDB): GCVE-100-312697

Entryinfo

Created: 06/17/2025 08:03
Updated: 09/27/2025 23:06
Changes: 06/17/2025 08:03 (52), 09/27/2025 23:06 (2)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!