DHS Political Appointees Asked CISA to Hack Voting Machine Without Vendor Notice
Sources tell ProPublica that Homeland Security officials sought a secret vulnerability assessment of voting equipment, a request that was never carried out.
Key points
- DHS political appointees requested CISA to hack a voting machine to find flaws.
- Officials wanted results reported to the White House without alerting the vendor.
- The request was made but was not acted upon by agency staff.
Political appointees at the Department of Homeland Security requested that the Cybersecurity and Infrastructure Security Agency hack a voting machine to identify security vulnerabilities, according to reporting by ProPublica. The officials wanted the findings sent directly to the White House without notifying the voting machine vendor, a request that was ultimately not carried out by agency personnel.
The request highlighted an unusual approach to vulnerability management within the department, where political leadership sought to bypass standard disclosure channels. ProPublica reported that the DHS officials wanted the agency to conduct the intrusion and report the results internally to the executive branch. The plan excluded the vendor from the notification process, a detail emphasized in the reporting as a key aspect of the unusual request made by political appointees.
Context and Background
This incident reflects broader shifts in how security flaws are managed by federal agencies, a trend that has been visible in other government programs. As Threat Times reported on October 19, 2026, the White House Gold Eagle Initiative was scaled back to a narrower triage role in August, indicating a move away from broad-scale vulnerability collection toward more targeted management. The DHS request to hack voting equipment without vendor notice occurred against this backdrop of evolving federal security strategies.
The reporting by ProPublica indicates that the request was specific to voting machines, a critical infrastructure category that typically receives heightened protection and coordination. By seeking to withhold notification from the vendor, the DHS officials proposed a method of handling vulnerabilities that differed from typical coordination. The fact that the request was made, even if not acted upon, suggests that internal pressures to control vulnerability information flow exist within the department.
Who Is Affected
The voting machine vendor was not informed of the request or any potential vulnerabilities, as the plan was never executed. Consequently, no specific systems or election jurisdictions were exposed to immediate risk from this particular unauthorized assessment attempt. However, the incident raises questions about the oversight mechanisms within DHS regarding how political appointees interact with technical agencies like CISA on sensitive infrastructure matters.
Election security stakeholders may view this report with concern, given the heightened scrutiny on voting systems in recent years. The fact that the request was made, even if not acted upon, suggests that internal pressures to control vulnerability information flow exist within the department. CISA staff’s decision not to act on the request indicates a adherence to established protocols, but the mere existence of the directive warrants attention from policymakers and security professionals monitoring government cybersecurity operations.
What should you do?
Security professionals should monitor official channels for updates on federal vulnerability disclosure policies. Organizations managing critical infrastructure should ensure their internal reporting lines for security incidents are clear and protected from political interference. Stakeholders should review existing coordination agreements with federal agencies to confirm that vendor notification remains a standard requirement in all vulnerability assessments.
What to do and how to stay safe: DHS
- Review internal protocols for reporting security vulnerabilities to ensure they align with federal coordination standards.
- Monitor updates from CISA and DHS regarding changes in vulnerability disclosure policies or political oversight mechanisms.
- Verify that vendor notification clauses are present in all agreements with federal agencies for security assessments.
- Encourage transparency in security testing by advocating for standard disclosure practices in industry forums.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
Did DHS officials successfully hack the voting machine?
No, according to ProPublica, the request to hack the voting machine was made but was not acted upon.
Why did DHS officials want to hide the vulnerabilities from the vendor?
The officials wanted to report the findings to the White House without telling the vendor, bypassing standard notification processes.
Is this related to the White House Gold Eagle Initiative?
Yes, as Threat Times reported on October 19, 2026, the Gold Eagle Initiative was scaled back, reflecting broader shifts in vulnerability management that contextualize this incident.
