Israel Espionage Threat Raised to Critical Amid NDAA Vote

As the Pentagon rates Israel’s espionage threat at the highest level it has ever assigned an ally, Congress is moving to hand Israel deeper access to America’s most sensitive military technology. Who is asking whether that makes sense?

The Defense Intelligence Agency does not hand out “critical” ratings lightly. In early June 2026, it did exactly that to Israel, and lawmakers are still voting on a defense bill that would expand cooperation anyway. That timing alone should raise questions in any newsroom, on any side of the aisle.

How Critical Is Israel’s Espionage Threat, According to the Pentagon?
The DIA’s internal assessment reportedly upgraded Israel’s counterintelligence threat designation from “high” to “critical,” the most serious category the agency uses, according to two current U.S. officials and one former official who spoke to NBC News. The New York Times later confirmed the reporting. Officials say the change was driven by concerns that Israeli intelligence services intensified efforts to learn what American officials were privately deciding about the war with Iran, going beyond what officials described as acceptable ally-to-ally intelligence gathering. Israel has publicly denied the characterization. Independent confirmation of every detail in the assessment is not yet public, and that is worth saying plainly. But the fact that a formal threat-level change occurred, and that it was reported by two separate outlets citing multiple officials, is not seriously in dispute.

What Is the NDAA Trying to Do?
While that assessment was circulating inside the Pentagon, the House was advancing Section 219 of the Fiscal Year 2027 National Defense Authorization Act, formally titled the United States-Israel Defense Technology Cooperation Initiative. The provision would direct the Pentagon to expand cooperation with Israel across artificial intelligence, quantum computing, autonomous systems, directed-energy weapons, cybersecurity and biotechnology. The House approved the rule advancing the underlying bill by a narrow 214-211 vote on July 21, with Section 219 still intact. A bipartisan group of lawmakers, led in part by Rep. Thomas Massie, has pushed to strip the language, arguing that terms like “network integration” and “data fusion” are not clearly defined and could make future oversight harder. The Senate’s companion version reportedly goes further still, pairing similar defense-technology language with intelligence-authorization provisions that would limit a future president’s ability to suspend or condition cooperation. Supporters call it an overdue modernization of a decades-old alliance. Critics call it a blank check written at the worst possible moment.

This Isn’t the First Time
None of this happens in a vacuum. The United States has a documented history of technology and intelligence losses connected to Israeli programs, and that history is why the DIA’s rating matters. In 1985, U.S. Navy intelligence analyst Jonathan Pollard was arrested for passing classified material to Israel; he served decades in prison before his sentence was commuted. In the late 1960s, the unresolved “Apollo Affair” centered on a large quantity of highly enriched uranium that went missing from a Pennsylvania nuclear fuel plant, NUMEC, prompting congressional and GAO investigations that never produced a definitive public conclusion. In the 1980s, employees connected to Israel Aircraft Industries were implicated in removing proprietary reconnaissance-camera documents from a U.S. defense contractor. Hollywood producer Arnon Milchan later confirmed publicly that he spent years acquiring sensitive technology for Israel’s nuclear program, including his role in the export of krytron switches, components capable of triggering nuclear devices. In 2001, Israeli firm NAPCO International pleaded guilty in a case involving illegally exported tank-armor technology. And Army engineer David Tenenbaum was investigated in the 1990s over information he shared with Israeli contacts; he was never prosecuted, later sued the Army alleging discriminatory scrutiny, and the case was ultimately settled. Israel is far from the only U.S. ally with a checkered intelligence history. But the pattern here is long, and it deserves to be weighed honestly rather than waved away.

Why Won’t Israel Share Iron Dome’s Secrets?
The United States has put more than $1.7 billion into Iron Dome since 2011, according to the Congressional Research Service, on top of billions more in broader missile-defense cooperation. Yet U.S. auditors have noted that Israel has withheld full technical data on the system it co-funded, even as American taxpayers underwrite its production. That is not a minor administrative gap. It is a one-way information flow, paid for by the public, that Congress rarely scrutinizes in the open. If the United States can fund a system without full access to its blueprints, what happens when the two militaries are “integrated” across AI and quantum computing instead of one missile interceptor?

Who Is Really Bearing the Risk?
Every dollar spent and every line of code shared under Section 219 rests on trust the Pentagon itself just downgraded. That is the contradiction at the center of this bill. If your own intelligence agency rates a partner’s espionage threat as critical, why would you hand that partner deeper access the same month? That is not a rhetorical trick. It is the question intelligence committees are supposed to ask before, not after, a vote.

When your own Pentagon rates a partner’s spying as “critical,” expanding that partner’s access isn’t oversight. It’s an open door.

$1.7 billion. That is the documented decade-long U.S. investment in Iron Dome alone [Congressional Research Service, cited by Roll Call]. The question no one on the House floor asked out loud: what is the United States getting back in technical transparency for that money?

Key Questions This Story Raises

• If the Pentagon’s own threat assessment says Israeli espionage activity is now “critical,” why is Congress simultaneously voting to expand access?
• Why has Israel historically declined to share full technical specifications for systems, like Iron Dome, that American taxpayers helped fund?
• Should any foreign defense-integration provision this broad be voted on inside a must-pass bill instead of debated on its own?

Congress is being asked to widen the door at the exact moment the Pentagon says it should be watching that door more closely. Whatever your view of the alliance itself, that timing deserves a floor debate, not a rider buried in a trillion-dollar bill.

What Do Supporters of This Policy Actually Believe?
Backers of Section 219, including groups like AIPAC, argue the initiative simply formalizes decades of already-close defense cooperation and helps both nations keep pace with China and other rivals in AI, quantum computing and cyber defense. They note that Israel remains a treaty-adjacent partner that has shared its own battlefield-tested technology, including missile-defense innovations, with the United States. That argument has real merit; Israeli research has genuinely strengthened American systems in the past. But merit on the technology-sharing side doesn’t answer the counterintelligence question. A partnership can be strategically valuable and still warrant tighter, more transparent oversight, especially the same month the partner’s threat rating gets upgraded. Supporters have not yet explained why that oversight can’t simply be added to the bill rather than left out of it.

Is This the Accountability Moment Congress Keeps Avoiding?
Lawmakers on both sides have had chances to slow this down and demand answers. Massie’s amendment to strip Section 219 failed to advance out of committee before being reintroduced on the floor. The Senate is expected to vote on cloture in the coming weeks, with its own version reportedly going even further by limiting future presidents’ ability to pause cooperation altogether. If that provision survives, it would not just expand today’s cooperation. It would make it harder for any future administration, of either party, to hit pause if another counterintelligence warning follows this one.

So which is it: is this the accountability moment American taxpayers have been waiting for, or another example of a defense bill moving too fast for anyone to actually read what’s inside it? The Pentagon has already told Congress what it thinks the risk looks like. The real question isn’t whether lawmakers saw that warning. It’s whether they’ll act on it before the vote is final.

What do you think — should Congress separate Section 219 from the NDAA and debate it on its own? Share this article and let us know.

Still have questions about what’s actually in the NDAA? Subscribe for daily coverage as this vote develops. Want your voice counted before the Senate votes? Contact your senators’ offices directly and ask where they stand on Section 219 and Section 1217.