Skip to content

AI finds vulnerabilities too fast and overloads corrections, alerts NSA and Wall Street

Lucas Montarroios
Lucas Montarroios

AI tools are detecting software failures in volume larger than teams can fix.

Loading audio…
Parede de concreto rachada coberta por dezenas de pequenas bandeirinhas laranja marcando cada fissura

Key takeaways

  • Ferramentas de IA detectam falhas de software em volume maior do que as equipes conseguem corrigir, alertam NSA e Wall Street.
  • A NSA e o setor financeiro de Wall Street relataram ao Congresso americano a sobrecarga gerada pela detecção acelerada de vulnerabilidades.
  • A correção de vulnerabilidades se tornou o gargalo: encontrar falhas ficou mais rápido do que remendá-las.
  • O avanço da IA muda a rotina de equipes de segurança no Brasil, que precisam lidar com mais alertas de falhas.

Artificial intelligence tools are locating software vulnerabilities at a pace that correction teams cannot keep up with. The side effect is counterintuitive: instead of making the systems safer immediately, the flood of alerts has overloaded the remediation processes. According to reports presented to the United States Congress by the NSA, the U.S. national security agency, and Wall Street executives, some recent technical flaws have been caused precisely by these correction efforts — as Gizmodo showed.

Why does AI find vulnerabilities much faster?

The difference is in scale and marginal cost. Traditional code analysis tools depended on manual written rules and sample human reviews. AI models can scan entire repositories, track data flow between modules, inspect third-party dependencies and point suspicious snippets in sequence, without each new scan costing the same as the previous one. More advanced agents can chain code reading, dependency analysis, and assemble a proof of attack concept. The practical result is a queue of findings that grows faster than any team can triage — and that is where the problem ceases to be technical and becomes operational.

What NSA and Wall Street reported about AI and vulnerabilities

According to the report published by Gizmodo, representatives of the NSA and executives of the US financial market described to legislators that recent technical incidents originated in their own efforts to correct identified vulnerabilities. It is the classic scenario of the emergency patch: a change applied under pressure, without the complete cycle of tests, in systems that cannot stay out of the air. When dozens of corrections need to be pushed at the same time into critical environments, the risk of one of them breaking compatibility, knocking down a service, or opening a new loophole increases proportionately. The report does not detail how many incidents occurred, which companies were affected or the size of the injury.

Why the correction of vulnerabilities has become the bottleneck

Finding is cheap; fixing is expensive. Each finding requires confirming whether it is truly exploitable, understanding the impact on the business, writing the correction, testing on approval, scheduling a maintenance window and communicating who depends on that system. In legacy environments, a single outdated library can appear in dozens of different services, multiplying the work. Therefore, prioritization is worth more than detection: public catalogues of failures with confirmed exploitation and actual exposure of the asset weigh more than the gross amount of alerts. Without this filter, AI produces a stack of tickets that nobody can close.

What Corrections Overload Changes to Teams in Brazil

The Brazilian cut tends to be more sensitive to bottleneck than the American one, because safety teams and platform teams are usually proportionally smaller. An average company that adopts AI scans without reinforcing the response team can simply exchange one risk for another: it becomes aware of hundreds of failures that it does not have the ability to correct in time. There is also regulatory pressure — LGPD requires short-term reporting of incidents with personal data, which transforms delay in correction into legal exposure. Those who operate AI agents internally already face similar problems on the governance side, a theme that appears in initiatives such as SailPoint Agentic Fabric in AWS Marketplace.

What is still unclear about AI and vulnerabilities

The report to Congress did not bring public figures: it is not known how many vulnerabilities are being discovered per month, what portion is really exploitable, nor how much of the problem stems from failures introduced by the corrections themselves. There is also no indication that regulatory agencies are preparing specific rules for the pace of disclosure of failures. Without these data, the discussion follows in the qualitative field — and the practical conclusion for now is that detecting faster without the ability to correct does not mean being safer.

Frequently Asked Questions about AI and vulnerabilities

The AI is creating vulnerabilities in the systems?

Not directly. What reports to Congress indicate is that corrections applied in haste to so many faults found can introduce new technical problems.

What is the main bottleneck today: finding or correcting flaws?

Correct. AI detection has become fast and cheap, while validation, testing and deployment continue to depend on human work and maintenance windows.

Should companies stop using AI to find security flaws?

Nope. The recommendation implicit in the reports is to adjust the process: prioritize what is really exploitable and ensure correction capacity before expanding the scan volume.

Share:

Source: gizmodo.com

Lucas Montarroios

Written by

Lucas Montarroios

Sou Lucas Montarroios e dediquei os últimos 15 anos à linha de frente de operações de telecom e data centers. Minha carreira sempre foi pautada por um foco implacável: transformar tecnologia e cenários críticos em oportunidades reais de negócio. No novidades.ia.br, trago essa visão executiva para o universo da IA. Especialista em produtos, mercado e ferramentas práticas de IA. Minha missão aqui é filtrar o ruído do mercado, analisando benchmarks, estratégias de grandes empresas e ferramentas práticas.

Related articles