NetworkConfiguration dhcpcd up to 10.3.2 Control Socket Operatingmode src/control.c control_recvdata 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.
3.5$0-$5k5.35

Summaryinfo

A vulnerability was found in NetworkConfiguration dhcpcd up to 10.3.2. It has been classified as critical. The impacted element is the function control_recvdata of the file src/control.c of the component Control Socket Operatingmode. This manipulation causes use after free. This vulnerability is registered as CVE-2026-56117. The attack needs to be launched locally. No exploit is available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as problematic was found in NetworkConfiguration dhcpcd up to 10.3.2. Affected by this vulnerability is the function control_recvdata of the file src/control.c of the component Control Socket Operatingmode. 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 availability. The summary by CVE is:

dhcpcd through 10.3.2, fixed in commit 78ea09e, contains a heap use-after-free vulnerability in the control socket handling within src/control.c that allows local unprivileged attackers to trigger memory corruption when privilege separation is disabled. Attackers can connect to the control socket and send a privileged command such as -x, causing control_recvdata() to free the client object while the same READ+HANGUP event subsequently reaches control_hangup() with the stale pointer, resulting in a use-after-free condition exploitable in deployments using --disable-privsep or where privsep initialization has failed with the control socket operating in mode 0666.

The weakness was published by CuB3y0nd as 78ea09ed1633a583dbcde6e7bab9df4639ec8a34. The advisory is shared at github.com. This vulnerability is known as CVE-2026-56117 since 06/18/2026. The exploitation appears to be difficult. An attack has to be approached locally. Technical details are known, but no exploit is available.

Upgrading eliminates this vulnerability. Applying the patch 78ea09ed1633a583dbcde6e7bab9df4639ec8a34 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

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

Productinfo

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒

CVSSv3info

VulDB Meta Base Score: 3.6
VulDB Meta Temp Score: 3.5

VulDB Base Score: 2.5
VulDB Temp Score: 2.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA Base Score: 4.7
CNA Vector (VulnCheck): 🔒

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: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Patch: 78ea09ed1633a583dbcde6e7bab9df4639ec8a34

Timelineinfo

06/18/2026 CVE reserved
06/23/2026 +5 days VulDB entry created
06/24/2026 +0 days Advisory disclosed
06/24/2026 +0 days VulDB entry last update

Sourcesinfo

Product: github.com

Advisory: 78ea09ed1633a583dbcde6e7bab9df4639ec8a34
Researcher: CuB3y0nd
Status: Confirmed

CVE: CVE-2026-56117 (🔒)
GCVE (CVE): GCVE-0-2026-56117
GCVE (VulDB): GCVE-100-373105

Entryinfo

Created: 06/24/2026 00:21
Changes: 06/24/2026 00:21 (81)
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!