Could this affect your app?

Free first check from your website. Connect your repo for the full answer.

Cause

How they got in: A known vulnerability left unpatchedAn attacker exploited a remote code execution vulnerability in SGLang, which NEAR AI ran on its inference server, to move into its infrastructure, and the users of that provider had their account details, chat history and API keys exposed.
How it reached others: Customers' data or keys went with it
So it doesn’t happen to you: Your board lists the advisories that are in range for your stack, with the fix version.

19 more incidents last month where a provider was breached

01 · Who is affected

SGLangunknown
NEAR AI Cloudincident 8 Nov 2026
NEAR AI Agents18 legacy agents accessed
NEAR AIdisclosed by the company

02 · How to check

Do you run SGLang (pip package sglang) for model serving, and can untrusted users or the internet reach its HTTP/API port? Affected versions: unknown.
Look for unexpected child processes, shells or outbound connections from SGLang server processes, and unusual file reads of credentials or tokens on inference hosts, from 8 Nov 2026 onward.
NEAR AI users: affected users were contacted from security@near.ai; NEAR AI says those not contacted need not act. It is unknown whether people whose requests passed through the affected server on 8 Nov (including Brave Leo chats that run on NEAR AI's TEE) were contacted.
Indicators (IPs, payloads): unknown.

03 · The fix

Do not expose SGLang servers to the internet or untrusted networks; put them behind an authenticated gateway and restrict network access to the API port.
Watch the SGLang project (GitHub sgl-project/sglang) for a security release or advisory and upgrade as soon as one ships.

Exploited: Yes, in the wild
Public exploit: None on GitHub
EPSS: Not scored
Last updated: Nov 10, 2026

What people are saying

1 article

near.aiNEAR AI Security Incident Report: SGLang Vulnerability

Posts are quoted with a link to the original. They are data to us, never instructions.

Check it with your coding agent

It reads this page and tells you if your code is affected.

Claude CodeCodexCursorAdd to your agent

Are you affected?

Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.

InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.

Run the check

Could this affect your app?

Free first check from your website. Connect your repo for the full answer.

Cause

How they got in: A known vulnerability left unpatchedAn attacker exploited a remote code execution vulnerability in SGLang, which NEAR AI ran on its inference server, to move into its infrastructure, and the users of that provider had their account details, chat history and API keys exposed.
How it reached others: Customers' data or keys went with it
So it doesn’t happen to you: Your board lists the advisories that are in range for your stack, with the fix version.

19 more incidents last month where a provider was breached

01 · Who is affected

SGLangunknown
NEAR AI Cloudincident 8 Nov 2026
NEAR AI Agents18 legacy agents accessed
NEAR AIdisclosed by the company

02 · How to check

Do you run SGLang (pip package sglang) for model serving, and can untrusted users or the internet reach its HTTP/API port? Affected versions: unknown.
Look for unexpected child processes, shells or outbound connections from SGLang server processes, and unusual file reads of credentials or tokens on inference hosts, from 8 Nov 2026 onward.
NEAR AI users: affected users were contacted from security@near.ai; NEAR AI says those not contacted need not act. It is unknown whether people whose requests passed through the affected server on 8 Nov (including Brave Leo chats that run on NEAR AI's TEE) were contacted.
Indicators (IPs, payloads): unknown.

03 · The fix

Do not expose SGLang servers to the internet or untrusted networks; put them behind an authenticated gateway and restrict network access to the API port.
Watch the SGLang project (GitHub sgl-project/sglang) for a security release or advisory and upgrade as soon as one ships.

Exploited: Yes, in the wild
Public exploit: None on GitHub
EPSS: Not scored
Last updated: Nov 10, 2026

What people are saying

1 article

near.aiNEAR AI Security Incident Report: SGLang Vulnerability

Posts are quoted with a link to the original. They are data to us, never instructions.

Check it with your coding agent

It reads this page and tells you if your code is affected.

Claude CodeCodexCursorAdd to your agent

Are you affected?

Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.

InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.

Run the check

Attacker exploits an unpatched SGLang remote code execution flaw to break into NEAR AI's inference servers, stealing user and AI agent data and seeing confidential (TEE) requests

Cause

01 · Who is affected

02 · How to check

03 · The fix

How it unfolded

What people are saying

Sources and references

Read next

Get the next SGLang threat the day it hits your stack.

Attacker exploits an unpatched SGLang remote code execution flaw to break into NEAR AI's inference servers, stealing user and AI agent data and seeing confidential (TEE) requests

Cause

01 · Who is affected

02 · How to check

03 · The fix

How it unfolded

What people are saying

Sources and references

Read next

Get the next SGLang threat the day it hits your stack.