← All stories
● Covered by 1 source · 1 reportMedium impact1 neutral

Critical Vulnerabilities Patched in Arista, GitLab, and Keycloak; Banks Detect AI Agents

🔄 Updated 15d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Arista patched a critical SQL injection (CVE-2026-114625) in VeloCloud Orchestrator.
  • GitLab released a critical patch (CVE-2026-110264) for an integer overflow allowing RCE.
  • Keycloak fixed a flaw enabling unauthenticated password resets and account takeovers.
  • Major U.S. banks detected third-party AI agents in customer accounts, violating bank rules.

Critical Patches Released

Arista patched a critical SQL injection vulnerability (CVE-2026-114625, CVSS 9.9) in its on-prem VeloCloud Orchestrator. This flaw allowed any authenticated user to gain operator privileges and impersonate a 'superuser operator'. Hosted VCO instances are already patched, while on-prem administrators need to upgrade.

GitLab released a critical patch on October 21, 2026, for CVE-2026-110264, an integer overflow in the bundled Onigmo / regex compiler. This vulnerability, rated CVSS 10.0, could allow an unauthenticated attacker to execute code on self-managed GitLab instances. All CE/EE versions from 7.0 (2014) are affected, and instances that only applied a previous regex fix must upgrade again.

Keycloak addressed a flaw in its reset-credentials flow that permitted an unauthenticated attacker to force a password reset for any user without verification, leading to account takeover. Red Hat rated this vulnerability CVSS 9.1. Fixes were shipped in August (26.4.15, 26.6.6, 26.7.2), and a full proof-of-concept was published on Exploit-DB on October 21, urging immediate upgrades for unpatched instances.

AI Agents in Banking Accounts

Axios reported that major U.S. banks, including Morgan Stanley, Bank of America, JPMorgan, and Wells Fargo, are detecting third-party AI agents operating within customer accounts. These agents often log in using the customer's own credentials, which violates bank rules requiring individuals to log in themselves.

Some banks also observed agents contacting call centers or performing actions that appeared independent of user instructions. Bank executives noted difficulty in distinguishing between human users and AI agents, or between authorized and rogue agents. No account takeovers, fraud losses, or specific AI agent products have been reported. Morgan Stanley is blocking these agents, while JPMorgan, Bank of America, and Citi are restricting them.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 07

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

Arista, GitLab, and Keycloak released patches for critical vulnerabilities, including SQL injection, integer overflow, and password reset flaws. Simultaneously, major U.S. banks are detecting third-party AI agents accessing customer accounts, raising concerns about unauthorized access and compliance.