SOCLYDE logo
Current languageEN
Cybersecurity newscybersecuritynear

NEAR AI reports access to agent data

NEAR AI describes an intrusion through SGLang affecting account records, legacy agents and API keys. Separate confirmed access from possible request exposure.

Published on

By Soclyde

A developer reviews her workstation before replacing API credentials

In summary

  • NEAR AI confirms access to records for about 100 users and 18 legacy agents.
  • Two Cloud customers had API keys exposed in logs; the keys were revoked.
  • Possible exposure of live requests does not establish access to all stored Private Chat histories.

Explore next

Soclyde resources

Article contents

NEAR AI said in its November 9, 2026 report that it had contained an intrusion through a remote code execution flaw in its SGLang inference engine. Confirmed access involved account information, legacy agents and API keys written to logs.

Account and agent data have separate scopes

NEAR AI reports downloaded records for about 100 users and access to histories, settings and logs for 18 agents on a legacy deployment outside its confidential enclave. Two Cloud customers had API keys in logs; those keys were revoked.

For your business, locate the notification and identify the exact application or agent. An account email address and an integration token require different changes in your tools.

Possible request exposure is not a general breach finding

The company says requests processed on November 8, including confidential-mode requests, could have been observed. It found no indication of access to stored Private Chat conversations or uploaded files.

Decrypt and The Block distinguish these data categories in their coverage. Avoid extending a notification about a legacy agent to every document your team has used with unrelated AI services.

The limit of confidential computing

NEAR AI explains that hardware isolation protects against the operator and host, without fixing a flaw in the software processing requests inside it. The company says it deployed a server-side fix; it does not name the exploited CVE.

If you host SGLang elsewhere, ask your provider which versions and measures apply. NEAR AI’s recovery does not establish that your own installation has received an equivalent correction.

Review integrations before reconnecting them

NEAR AI says it replaced credentials and tokens and notified identified users. For a business integration, check which secret it uses and whether the previous access remains active at the issuing service.

After replacement, test a normal operation and examine logs without copying the new key into them. Be wary of messages referencing a balance or account name to persuade you to disclose a secret.

The connection with Soclyde

Keys copied into logs become sensitive data held in multiple systems. Soclyde keeps secrets in an encrypted vault on your devices and helps reduce their spread across notes and messages.

Once an application uses a key, that application must handle it correctly too. Soclyde does not remove copies already in logs or revoke NEAR AI access on your behalf.

What to remember

Connect each notification to the accounts, agents and integrations actually in use. To organize an access review for your business, contact Soclyde with a description of the need, without sending a key or password.

Frequently asked questions

Were all conversation histories stolen?

No. NEAR AI distinguishes the histories of 18 legacy agents from stored Private Chat conversations, for which it found no indication of access.

Which SGLang vulnerability was exploited?

The report names neither a CVE nor an affected version. It describes a fix on NEAR AI servers without identifying a universally corrected upstream version.

What if my business had a key in the logs?

Follow the notification, replace the key at its issuing service and update integrations. Review use of the old key and remove secrets from logs.

References

Sources and references

Need advice?

Design your password strategy with Soclyde

Schedule a dedicated walkthrough with the team to see how local-first security adapts to your stack.

Talk with us

Keep reading