NEAR AI Contains Security Breach After SGLang Vulnerability Exploitation
- Published
- Updated
NEAR AI said an unauthorized party exploited an SGLang remote code execution flaw and reached one inference server and internal infrastructure. The company later restored cloud services after the incident, while also disclosing exposure of user account details, legacy agent chat history and logs, and API keys for two customers.
Key claims & sources
What it means
NEAR AI runs inference infrastructure built on SGLang, an open-source engine, so a flaw in that layer can reach the systems that serve customer workloads. The November 9 incident report places this event in the context of a live service environment, not a theoretical test case. For builders using hosted AI services, the episode is a reminder that the security boundary includes the inference stack as well as the application layer.
For users and customers, the immediate issue is exposure of account details, chat history, logs, and API keys rather than a visible product feature change. Revoked keys mean integrations and automated workflows may need to be recreated or rotated before they work again. The restoration of cloud service suggests normal operations resumed, but the affected data and credentials still matter for anyone relying on the platform.
This case sits at the intersection of AI infrastructure and security hygiene, where a single remote code execution flaw can reach both service delivery and stored customer data. It also shows how quickly trust in managed AI tooling can depend on how operators isolate inference servers from internal systems. The trade-off is clear: centralized cloud AI services are convenient, but they also concentrate operational and security risk in one place.
Still unknown is the full scope of what the attacker accessed beyond the inference server, and whether any other data or systems were touched. The incident report described one path into internal infrastructure, but not every downstream step or the complete set of impacted customers. Further detail would come from a fuller postmortem, including the exact affected components and the remediation steps taken after the November 9 report.
Market reaction i
NEAR Protocol fell 1.1% in the 4 hours after the first headline, after rising 1.4% in the 2 hours before.
40 prices, one every 30 minutes · The move was larger before the first headline than after: an observation, not an explanation. The market also moves on things nobody publishes.
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Other recent incidents
| When | What happened | Figure |
|---|---|---|
| today | Initia · Private key leak incident | $615k |
| 2 days ago | Swarm · Supply chain attack incident | no figure in dollars |
| 2 days ago | Ankr Bridge · Cross-Chain Message Spoofing incident | $304.5k |
| 3 days ago | ACryptoS · Missing Input Validation incident | $665.4k |
| 3 days ago | LNbits · Software vulnerability incident | $1.7k |
4296 incidents stored