From ~2019 to 2024, CISA conducted technical and operational activities to evaluate certain US election systems, all upon request of system owners/operators, including software examination, penetration testing of SLTT (state, local, tribal, and territorial) networks, and incident response for election-system intrusions (p.1).
p.1Election Report (CISA)
Key Insights
AI-generated from the sourced claims — verify against the documents.
Structural constraints in the certification ecosystem limit vendors' ability to patch quickly; some certification regimes require that no patches be applied for months before an election, so systems are deployed with known, unpatched issues.
In multiple cases CISA assessors gained full network control within hours or days, showing many SLTT partners remain 'soft targets'.
Vendor threat models assume strong segmentation between election systems and enterprise IT, but 2019-2024 assessments showed election systems reachable from enterprise hosts via shared auth domains, legacy VLANs, or 'temporary' exceptions; poor firewall hygiene; co-location on general-purpose virtualization clusters; and unreliable 'airgap' assumptions.
The Critical Product Evaluation program created disincentives for transparent, industry-standard vulnerability disclosure; it was retired in 2024 based on stakeholder feedback.
In 2020, ImageCast X Ballot Marking Devices printed ballots encoding selections in a barcode voters could not verify, and a researcher showed hackers could change the barcode-encoded votes without physical machine access.
22 sourced claims
CISA notified the owner/operator in every case it identified a vulnerability in a product or network and encouraged mitigation (p.1).
p.1Structural constraints in the certification ecosystem limit vendors' ability to patch quickly; some certification regimes require that no patches be applied for months before an election, so systems are deployed with known, unpatched issues (p.1).
p.1SLTT election-office IT networks frequently lack cybersecurity hygiene; election infrastructure is often accessible from general enterprise networks, enabling lateral movement by adversaries who compromise email, workstations, or other IT assets (p.1).
p.1US election security is shaped by three factors: (1) software vulnerability management constrained by outdated certification regimes; (2) inconsistent vendor transparency on vulnerabilities and patch status; (3) cybersecurity immaturity of many SLTT networks (p.1).
p.1From 2019-2024 CISA partnered with Idaho National Laboratory (INL) on the Critical Product Evaluation program for direct technical assessments of election software, often before public release, upon vendor request (p.2).
p.2Assessment methods included static source-code review, binary fuzzing of parsers/media handling/data import modules, cryptographic implementation analysis (PRNG misuse, poor key handling), interface/authentication/authorization/API testing, supply-chain dependency reviews, and dynamic analysis in adversarial runtime environments (p.2).
p.2The Critical Product Evaluation program created disincentives for transparent, industry-standard vulnerability disclosure; it was retired in 2024 based on stakeholder feedback, with final reporting concluding in 2025 (p.3).
p.3Vulnerabilities found included input-validation bugs, insecure deserialization, insufficient logging, race conditions, insecure crypto primitives, and privilege-escalation paths; CISA did not independently validate whether production builds in SLTT environments incorporated all fixes (p.3).
p.3SLTT officials face update difficulties due to minimal IT budgets/staff, short deployment windows, and "lockdown" periods (sometimes mandated by state law) barring changes before election day; state laws may require only EAC (Election Assistance Commission)-certified software, delaying updates that postdate certification (p.3).
p.3Technical risks: vendors cannot ship fixes outside narrow certification cycles without jeopardizing eligibility; third-party components (OS, drivers, middleware, crypto libraries) cannot be patched at modern cadence; legacy OS baselines accumulate unpatched vulnerabilities; absence of secure auto-update prevents rapid zero-day response (p.3).
p.3CISA recommends national policymakers encourage harmonization of patch-management and certification rules (p.4).
p.4Across penetration tests and red-team engagements, CISA observed flat/minimally segmented networks, weak identity and access management (poor MFA, shared credentials, weak service-account hygiene), lack of endpoint hardening, legacy remote-access/file-transfer pathways, and insufficient traffic monitoring (p.4).
p.4In multiple cases CISA assessors gained full network control within hours or days, showing many SLTT partners remain "soft targets" (p.4).
p.4Most states have moved away from paperless electronic voting machines; in 2020, ImageCast X Ballot Marking Devices printed ballots encoding selections in a barcode voters could not verify, and a researcher showed hackers could change the barcode-encoded votes without physical machine access (p.4).
p.4Citation given: J. Alex Halderman, Security Analysis of Georgia's ImageCast X Ballot Marking Devices, expert report in Curling v. Raffensperger (Civil Action No. 1:17-CV-2989-AT, N.D. Ga.), with Drew Springall, July 1, 2021 (p.4).
p.4ODNI commissioned a forensic examination of Dominion Voting Systems devices used in Puerto Rico's 2024 election; CISA reviewed the report but did not have access to the devices and could not perform its own examination (p.4).
p.4Citation given: Dominion Voting Systems Democracy Suite Preliminary Vulnerability Assessment, Mojave Research for the ODNI, September 25, 2025 (p.4).
p.4Vendor threat models assume strong segmentation between election systems (voter-registration databases, e-pollbooks, election management/tabulation systems, central scanning) and enterprise IT, but 2019-2024 assessments showed election systems reachable from enterprise hosts via shared auth domains, legacy VLANs, or "temporary" exceptions; poor firewall hygiene; co-location on general-purpose virtualization clusters; and unreliable "airgap" assumptions (vendor support tunnels, remote-management tools) (p.5).
p.5CISA recommended mitigations: harmonize patch/certification rules; adhere to CISA Best Practices for Securing Election Systems; use human-readable paper ballots; conduct post-election manual audits of paper ballots before certification (p.5-6).
p.5Additional recommendations: encourage vendors to assign CVE numbers, notify customers if source code is leaked/stolen, report incidents to authorities, include a software bill of materials (SBOM); and ensure transparent documentation of all security incidents and remediation (p.6).
p.6Conclusion: US election-system security issues stem from complex interdependencies between vendors, certifiers, policymakers, and resource-constrained SLTT partners, not any single entity (p.6).
p.6Reporting at the time
External context — third-party coverage published around these events, linked for reference. Separate from the primary documents.
Page evidence
Election Report (CISA) · p.1

Page OCR text
ELECTION REPORT y EXECUTIVE SUMMARY From around 2019 to 2024, the Cybersecurity and Infrastructure Security Agency (CISA) conducted a set of technical and operational activities to evaluate the security of certain U.S. election systems. These activities, all carried out upon the request of system owners and operators, included direct examination of election-related software; penetration testing of state, local, tribal, and territorial (SLTT) networks; and incident response operations for intrusions into elections systems. Through these activities, CISA developed a strong understanding of the vulnerabilities that, at the time of testing, affected select election-related software products and network environments evaluated by CISA. In every software product or election-related network in which CISA identified a vulnerability, CISA notified the owner or operator of the vulnerable product or network and encouraged them to mitigate the vulnerability. CISA’s findings highlight the reality that election-related software, like all complex software, contains vulnerabilities that require timely remediation. While past partnerships with election vendors enabled early identification of security weaknesses prior to product release, structural constraints in the certification ecosystem significantly limit vendors’ abilities to patch systems quickly. For example, some government election systems certification regimes require that no patches be applied for months before an election. These limitations, combined with inconsistent vulnerability disclosure practices, result in election systems being deployed with known and unpatched security issues. Beyond software quality, CISA’s assessments repeatedly show that the IT networks operated by SLTT election offices lack cybersecurity hygiene. Many election vendor threat models assume strong network segmentation and isolation of election systems. However, in practice, election infrastructure is often accessible from general enterprise networks, creating opportunities for lateral movement by adversaries who compromise email systems, user workstations, or other information technology (IT) assets. Weak identity management, limited logging, and insufficient segmentation exacerbate the risk that a cyber threat actor could access or disrupt mission critical election IT components. Overall, the security of U.S. elections is shaped by the interaction of three major factors: (1) software vulnerability management constrained by outdated certification regimes; (2) inconsistent transparency from election system vendors on vulnerabilities and patch status; and (3) the cybersecurity immaturity of many SLTT networks responsible for hosting election systems. Addressing these challenges requires coordinated action across technical, policy, and regulatory domains. This report provides detailed analysis and proposes targeted recommendations to strengthen election infrastructure security and enhance public trust in the resilience of the nation’s elections infrastructure. W98 cisa.gov Wa central@cisa.dhs.gov XX @cisagov | @ciSACyber ‘in) £) @cisagov As of July 13, 2026