The Department of Homeland Security is caught between two conflicting federal court orders over changes to the SAVE verification system, with one judge demanding the system’s SSN-search and bulk-upload features be restored while another has ruled those same changes unlawful; the result is a legal logjam that appears headed for appellate review and could reach the Supreme Court.
“Damned if you do, damned if you don’t” might never have been a more fitting description than for the current predicament in which the Department of Homeland Security (DHS) now finds itself. The Department is now faced with dueling orders from two different District Court judges — and complying with one means violating the other. That conflict puts DHS in the middle of a rare and uncomfortable judicial squeeze.
The background starts with modifications to the Systematic Alien Verification for Entitlements, or SAVE, intended to let agencies verify immigration status more efficiently. One federal judge concluded those changes ran afoul of the Privacy Act, the Social Security Act, and the Administrative Procedure Act, and effectively vacated the expanded features. That ruling immediately prompted DST to disable the newly added capabilities nationwide.
Separately, a long-running dispute with the State of Florida produced a settlement in late 2025 that required DHS to upgrade SAVE to permit searches using full and last-four SSNs and to process bulk uploads. The Florida case was resolved by agreement, and the approving judge retained jurisdiction for two decades to ensure enforcement of that deal. The gulf between the settlement terms and the later vacatur quickly became the source of the current clash.
The amended complaint alleged that the SAVE system was an “inadequate tool” to verify immigration status because it required a “unique immigration identifier” to run an inquiry, and it could not run an inquiry using a Social Security number (SSN), driver’s license number, or other similar identifier.
The case was resolved by a settlement agreement executed by the parties in November 2025. The agreement required the parties to cooperate on “improving and modernizing” the SAVE system, and among other things, it required Defendants to ensure that the system had the capability to (1) “[i]ntegrat[e] with the Social Security Administration to allow searches with full [SSNs] to be used as a non-DHS enumerator”; (2) “[i]ntegrat[e] with the Social Security Administration to allow searches with last-four-digits SSNs to be used as a non-DHS enumerator”; and (3) “process bulk upload verification requests so that users of the system will not need to input verification requests one-by-one.”
When Florida returned to court to enforce that settlement after the SAVE features were disabled, the Northern District of Florida judge found DHS in breach and ordered the agency to restore the SSN-search and bulk-upload functions immediately. That order rests on the settlement language and the judge’s view that the prior deal obligates DHS to maintain those capabilities. The judge also expressly rejected the opposing district court’s interpretation of federal privacy and Social Security statutes.
This Court is not bound by Judge Sooknanan’s order, and with all due respect, the Court disagrees with the conclusions in that order. For example, with respect to the Social Security Act, even though 42 U.S.C. §405(c)(2)(C)(viii)(I) seemingly precludes the Social Security Administration (SSA) from disclosing SSNs to anyone, that statute does not preclude SSA from doing so in the immigration context because SSNs can provide information about citizenship and 8 U.S.C. §1373(a) expressly provides that “[n]otwithstanding any other provision of Federal … law, a Federal … entity or official may not … in any way restrict[] any government entity or official from sending to … [Defendants] information regarding the citizenship or immigration status, lawful or unlawful, of any individual.” (emphasis added). Moreover, with respect to the Privacy Act, the modifications to the SAVE system plainly fall within the Act’s “routine use” exception in 5 U.S.C. §552a(a)(7), (b)(3), because using SSNs to verify the identity of potential non-citizens is not incompatible with the purpose of SSNs (e.g., “to establish the age, citizenship, or alien status and true identity” of individuals, see 42 U.S.C. §405(c)(2)(B)(ii)), and it is undisputed that Defendants published notice of the use of SSNs as part of the modified SAVE system in advance of the order approving the settlement agreement requiring integration of the SSN-search feature.
The Northern District judge also acknowledged the practical dilemma for DHS, saying the agency faces two directly conflicting court orders and that one must give. The judge was unswayed by DHS’s argument that his order should yield, and he made clear he believes the settlement-backed enforcement was the correct legal path. That posture effectively forces DHS to pick which judicial command to follow or to seek relief by appealing.
DHS has appealed the vacatur to the D.C. Circuit, and the agency is likely to challenge the enforcement order in the 11th Circuit as well. On appeal, the agency can present the competing directives and press for resolution of which ruling should control. Appellate courts will be asked to weigh statutory text, settlement obligations, and privacy protections in the context of migration verification tools.
The interstate dimension complicates matters: a settlement reached with one state and enforced in one circuit can collide with a different circuit’s ruling on federal privacy law. When two district courts issue incompatible mandates like this—one ordering deactivation and the other restoration—only higher courts can provide a uniform answer. That raises the prospect of en banc review or, ultimately, Supreme Court intervention.
The practical stakes are significant for agencies and state partners that rely on SAVE to screen benefits eligibility and verify immigration status quickly. Any prolonged uncertainty will affect operations across multiple jurisdictions while courts sort out whether the SAVE changes were lawfully implemented, contractually required, or improperly adopted. Meanwhile, DHS must navigate compliance risks as it evaluates appellate options and potential routes for reconciling the conflicting orders.
Add comment