PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-7067 D-Link CVE debrief

CVE-2026-7067 is a command injection vulnerability in the udhcpd DHCP Service of D-Link DIR-822 A1. The vulnerability is caused by manipulation of the Hostname argument in the /udhcpcd/dhcpd.c file. The attack can be initiated remotely and has been publicly disclosed. This vulnerability only affects products that are no longer supported by the maintainer.

Vendor
D-Link
Product
DIR-822
CVSS
MEDIUM 5.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-04-27
Original CVE updated
2026-10-26
Advisory published
2026-04-27
Advisory updated
2026-10-26

Who should care

Defenders responsible for D-Link DIR-822 A1 devices should assess potential remote attack vectors and verify exposure. They should prioritize verifying exposure of these devices and assessing potential remote attack vectors to address this vulnerability effectively and prevent exploitation attempts by malicious actors seeking to inject commands. Security teams and vulnerability management teams should also be aware of the potential impacts and take steps.

Why it matters

CVE-2026-7067 is a command injection vulnerability in D-Link DIR-822 A1 devices that can be exploited remotely. Defenders should prioritize verifying exposure and assessing potential remote attack vectors.

  • Remote attackers may exploit this vulnerability to inject commands
  • Defenders should verify exposure of D-Link DIR-822 A1 devices
  • Device configurations may need to be reviewed and updated to prevent exploitation
  • Remediation priority is high due to public disclosure of the exploit

Technical summary

The vulnerability is caused by manipulation of the Hostname argument in the /udhcpcd/dhcpd.c file of the udhcpd DHCP Service in D-Link DIR-822 A1. The attack can be initiated remotely and has been publicly disclosed. This vulnerability only affects products that are no longer supported by the maintainer. Defenders should prioritize verifying exposure and assessing potential remote attack vectors to address this vulnerability effectively and prevent exploitation attempts by malicious actors seeking to inject commands.

Defensive priority

Defenders should prioritize verifying exposure of D-Link DIR-822 A1 devices and assessing potential remote attack vectors.

Recommended defensive actions

  • Verify exposure of D-Link DIR-822 A1 devices
  • Assess potential remote attack vectors
  • Review and update device configurations to prevent exploitation
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD vulnerability detail provide information on the vulnerability, including its description, CVSS score, and affected products. The vulnerability only affects products that are no longer supported by the maintainer. Defenders should verify exposure of D-Link DIR-822 A1 devices and assess potential remote attack vectors. The exploit has been publicly disclosed and may be utilized.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-7067 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-7067

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-7067 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-7067

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.