CVE-2026-49139

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-06-01 21:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-07-22 08:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.4% in the next 30 days (EPSS).
• Severity: 7.0 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-06-01 21:16 UTC

Last modified

2026-07-22 08:10 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-918 · Server-side request forgery

Record status

Deferred

Attack profile CVSS 4.0 · 7.0

Attack vector

Network

Complexity

Low

Attack requirements

Present

Privileges needed

None

User interaction

None

Confidentiality

None

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-49139.md and follow it. Check whether this project is affected by CVE-2026-49139. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge