The Pulse
NVIDIA Rotates Brev SSH Keys After 16-Day Security Incident
NVIDIA says unauthorized activity on its Brev cloud platform between October 4 and October 20 may have exposed SSH keys provisioned for customer virtual machines. The company rotated the keys and updated customer instances, but its investig
AI.info Team · Written with AI · fact-checked ·
A notice to affected Brev customers says information on NVIDIA’s cloud development platform may have been exposed during unauthorized activity from October 4 through October 20. The notice identifies SSH keys provisioned for customer virtual machines as potentially affected. NVIDIA says it rotated the keys and updated customer instances with replacements.
“Our analysis determined that your information from our Brev network may have been affected. This SSH key has since been rotated, and your instances have been updated with the replacement key.”
The NVIDIA customer notification, quoted by Tom’s Hardware
What the Brev notice says about the incident
The 16-day period is the window of unauthorized activity identified by NVIDIA’s investigation, according to the customer notice described by Tom’s Hardware. The report says some accounts may have been exposed, and that information stored on Brev could have been accessible to malicious actors. It does not establish that every customer or virtual machine was affected.
NVIDIA says it found no evidence that the keys were improperly used. The company has not explained how the unauthorized activity began or disclosed whether customer data or workloads were accessed. Those limits leave the confirmed response clearer than the extent of any customer impact: keys were replaced, but the report does not specify what information, if any, attackers obtained.
SSH keys can provide access to customer machines
Brev uses SSH keys to help customers connect to virtual machines in the cloud. Developers and system administrators use SSH connections to manage remote machines, transfer files and run commands, without being physically present at the computers. The keys therefore serve as credentials for accessing customer instances.
Tom’s Hardware notes that access through an exposed key could potentially let an attacker take control of a virtual machine, depending on the permissions attached to it and other security controls. That is a possibility, not evidence that an attacker entered a customer machine. The available account of NVIDIA’s investigation says it found no evidence of improper use of the keys.
Wiz adds Brev to its October incident roundup
The Brev disclosure follows a month in which other AI development platforms also reported security incidents. In a blog post published October 30, cybersecurity firm Wiz initially listed at least nine platforms with incidents during October. A later edit added Brev and Trigger.dev as additional publicly reported incidents.
Wiz said the public accounts it reviewed described targeted attempts to find stored environment variables, with a focus on credentials that grant access to AI services. The firm also cautioned that the incidents do not share a single identified vulnerability or dependency. Its roundup provides context for the Brev notice, but does not establish a connection between NVIDIA’s incident and the other platform cases.
Key replacement does not answer every impact question
NVIDIA’s stated remediation covers the SSH key it provisioned for affected Brev virtual machines: the key was rotated and the instances were updated. The customer notice, as quoted in the report, does not detail the investigation’s methods or say whether anyone attempted to use the keys before rotation. It also does not describe whether customer workloads or data were accessed.
For customers, the distinction is between a credential that may have been exposed and confirmed misuse. NVIDIA’s reported finding addresses the latter only as an absence of evidence; it does not resolve the exposure question for each customer or machine. The incident account available on November 2 establishes the activity window and key replacement, while leaving the access path and any further impact unspecified.