AI Flaw Reporting and Security Enhancement Act

To direct the Director of the National Institute of Standards and Technology to develop a program for the voluntary reporting of artificial intelligence flaws and the acceleration of detection and monitoring of such flaws, and for other purposes.

  1. Introduced
  2. Committee
  3. Passed House
  4. Passed Senate
  5. To President
  6. Became law
Sponsor Rep. Ross, Deborah K. [D-NC-2] Introduced June 18, 2026 Cosponsors 2 (1 D, 1 R) Latest action June 25, 2026

Summary

AI Flaw Reporting and Security Enhancement Act
This bill establishes a program to facilitate the voluntary reporting and tracking of artificial intelligence (AI) flaws, to be administered by the National Institute of Standards and Technology (NIST).
In carrying out this program, NIST must seek to convene various stakeholders to establish common definitions for terms related to AI flaws and criteria for the classification of AI flaws (e.g., security-related flaws and safety-related flaws). The group must also support the development of technical standards and guidance related to detecting, managing, and disclosing AI flaws and prioritizing the remediation of such flaws.
Further, NIST must develop, or enter into cooperative agreements with institutions of higher education or research institutions to develop, infrastructure for the voluntary reporting, collection, and tracking of AI flaws. This must include a national database of AI flaws or the modification of an existing national database to account for AI flaws. (NIST currently administers a national database of cybersecurity vulnerabilities.) NIST must consider certain topics when developing this infrastructure, including the interoperability of the infrastructure with relevant existing systems, standards, and best practices.
Within three years of the bill’s enactment, NIST must report to Congress on the implementation of these provisions.
Under the bill, an AI flaw is a set of conditions or behaviors that allow for the violation of certain policies (e.g., safety or security policies) and is not necessarily associated with malicious intent.

Summary by the Congressional Research Service, Library of Congress.

Congress.gov

Actions

  1. Jun 25, 2026 Ordered to be Reported in the Nature of a Substitute by the Yeas and Nays: 35 - 0.
  2. Jun 25, 2026 Committee Consideration and Mark-up Session Held
  3. Jun 18, 2026 Referred to the House Committee on Science, Space, and Technology.
  4. Jun 18, 2026 Introduced in House

Congressional and federal records come from official public sources: the House Clerk, the U.S. Senate, GovInfo and the Library of Congress (bill status), the Federal Register, and the congress-legislators project. They are copied on a schedule and may lag the official record by a few hours; the official sources govern. News and coverage counts are drawn from the 4Conservative index and reflect what the press published, not 4Conservative's views. Nothing here is an endorsement of any candidate, party or position. Terms of use.