Description
Nanobot prior to version 0.2.1 contains a server-side request forgery vulnerability in the Microsoft Teams channel handler that allows remote attackers to exfiltrate Bot Framework bearer tokens by supplying a forged activity with an attacker-controlled serviceUrl value. Attackers can poison the stored conversation reference by sending a crafted inbound activity to the Teams webhook, causing subsequent bot replies to transmit token-bearing Authorization header requests to an attacker-controlled host.
Published: 2026-06-01
Score: 7 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Prior to version 0.2.1, Nanobot’s Microsoft Teams channel handler blindly follows any serviceUrl supplied in an incoming activity. An attacker can forge the serviceUrl field so that it points to an attacker‑controlled endpoint. When the bot later replies on the same conversation, the framework includes the stored Authorization header containing a bearer token, causing the bot to send that token to the attacker’s host. The result is a server‑side request forgery that exposes confidential Bot Framework credentials and allows the attacker to perform authenticated actions on the bot’s behalf. This vulnerability is categorized as CWE‑918: Server‑Side Request Forgery.

Affected Systems

The vulnerability affects the Nanobot project of the HKUDS organization. All releases prior to 0.2.1 are vulnerable; version 0.2.1 and later contain the fix.

Risk and Exploitability

The CVSS score of 7 indicates a high severity. No EPSS data is available, so the exploitation probability cannot be precisely quantified, but the attack does not require privileged access and can be triggered via the Teams webhook endpoint. The vulnerability is not listed in CISA’s KEV catalog. Attackers can execute the exploitation remotely by sending a crafted activity to the Teams webhook URL; no credentials or local installation are needed.

Generated by OpenCVE AI on June 1, 2026 at 21:37 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Nanobot to version 0.2.1 or newer
  • Implement strict validation on the serviceUrl field to allow only trusted Microsoft Teams URLs and reject arbitrary hosts
  • If an upgrade is not possible immediately, temporarily disable or remove the Microsoft Teams channel integration
  • Restrict outbound network traffic from the bot so that it can only reach allowed hosts; monitor for outbound HTTP requests containing Authorization headers

Generated by OpenCVE AI on June 1, 2026 at 21:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 02 Jun 2026 18:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 01 Jun 2026 22:15:00 +0000

Type Values Removed Values Added
First Time appeared Hkuds
Hkuds nanobot
Vendors & Products Hkuds
Hkuds nanobot

Mon, 01 Jun 2026 20:30:00 +0000

Type Values Removed Values Added
Description Nanobot prior to version 0.2.1 contains a server-side request forgery vulnerability in the Microsoft Teams channel handler that allows remote attackers to exfiltrate Bot Framework bearer tokens by supplying a forged activity with an attacker-controlled serviceUrl value. Attackers can poison the stored conversation reference by sending a crafted inbound activity to the Teams webhook, causing subsequent bot replies to transmit token-bearing Authorization header requests to an attacker-controlled host.
Title Nanobot < 0.2.1 SSRF via Microsoft Teams Channel serviceUrl Poisoning
Weaknesses CWE-918
References
Metrics cvssV4_0

{'score': 7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:H/SI:H/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-06-02T15:46:15.707Z

Reserved: 2026-05-27T17:40:12.738Z

Link: CVE-2026-49139

cve-icon Vulnrichment

Updated: 2026-06-02T15:27:17.695Z

cve-icon NVD

Status : Deferred

Published: 2026-06-01T21:16:46.913

Modified: 2026-06-02T14:43:49.920

Link: CVE-2026-49139

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-01T22:00:12Z

Weaknesses