CVE-2026-49139

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 69% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity70% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

June 1, 2026

Last Modified

July 22, 2026

Advisory Details (4)

Auto-updated Jun 11, 2026
Patch available. Sources: github_release, github_pr, github_commit.
generic

Nanobot < 0.2.1 SSRF via Microsoft Teams Channel serviceUrl Poisoning | Advisories | VulnCheck

https://www.vulncheck.com/advisories/nanobot-ssrf-via-microsoft-teams-channel-serviceurl-poisoning
github_commit Patch Available

commit 232df45126bc (HKUDS/nanobot)

Patch available: HKUDS/nanobot v0.2.1 (contains commit 232df45126bc)

https://github.com/HKUDS/nanobot/commit/232df45126bcf0f8fccd123d73714f202c8e8612
github_pr Patch Available

[security] fix(msteams): trust service URLs before replies

Patch available: HKUDS/nanobot v0.2.1 (PR #4047 merged 2026-05-29)

https://github.com/HKUDS/nanobot/pull/4047
github_release Patch Available

v0.2.1

Patch available: HKUDS/nanobot v0.2.1

https://github.com/HKUDS/nanobot/releases/tag/v0.2.1

Vendor Advisories for CVE-2026-49139(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 50× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 133 total refreshes for this CVE.

  1. 2026-07-26 23:14 UTCEG score recompute
  2. 2026-07-26 23:14 UTCGHSA enrichment
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-25 14:18 UTCEPSS rescore
  5. 2026-07-24 14:18 UTCEPSS rescore
  6. 2026-07-23 14:18 UTCEPSS rescore
  7. 2026-07-23 03:18 UTCEG score recompute
  8. 2026-07-22 14:08 UTCEPSS rescore
  9. 2026-07-21 15:25 UTCEPSS rescore
  10. 2026-07-20 17:08 UTCEPSS rescore
  11. 2026-07-19 14:31 UTCEPSS rescore
  12. 2026-07-19 14:31 UTCEPSS rescore
  13. 2026-07-19 02:29 UTCEPSS rescore
  14. 2026-07-18 10:04 UTCEPSS rescore
  15. 2026-07-16 17:03 UTCEPSS rescore
  16. 2026-07-16 01:27 UTCGHSA enrichment
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-14 16:54 UTCGHSA enrichment
  20. 2026-07-14 05:22 UTCGHSA enrichment
  21. 2026-07-13 22:30 UTCEPSS rescore
  22. 2026-07-13 06:13 UTCEPSS rescore
  23. 2026-07-12 05:46 UTCEPSS rescore
  24. 2026-07-12 00:49 UTCGHSA enrichment
  25. 2026-07-11 13:23 UTCGHSA enrichment
Show 75 more
  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-08 16:51 UTCGHSA enrichment
  4. 2026-07-08 15:16 UTCEPSS rescore
  5. 2026-07-07 13:46 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-02 13:52 UTCGHSA enrichment
  10. 2026-07-02 01:49 UTCGHSA enrichment
  11. 2026-07-01 15:07 UTCEPSS rescore
  12. 2026-07-01 10:43 UTCGHSA enrichment
  13. 2026-06-30 23:22 UTCEPSS rescore
  14. 2026-06-30 23:18 UTCGHSA enrichment
  15. 2026-06-30 00:27 UTCGHSA enrichment
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-29 14:06 UTCEPSS rescore
  18. 2026-06-29 12:10 UTCGHSA enrichment
  19. 2026-06-29 00:45 UTCGHSA enrichment
  20. 2026-06-28 14:07 UTCEPSS rescore
  21. 2026-06-28 13:21 UTCGHSA enrichment
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-28 01:56 UTCGHSA enrichment
  25. 2026-06-27 14:32 UTCGHSA enrichment
  26. 2026-06-27 03:08 UTCEPSS rescore
  27. 2026-06-27 03:08 UTCGHSA enrichment
  28. 2026-06-26 15:32 UTCGHSA enrichment
  29. 2026-06-26 01:35 UTCGHSA enrichment
  30. 2026-06-25 13:49 UTCEPSS rescore
  31. 2026-06-25 13:40 UTCGHSA enrichment
  32. 2026-06-25 02:16 UTCGHSA enrichment
  33. 2026-06-24 14:52 UTCGHSA enrichment
  34. 2026-06-24 14:05 UTCEPSS rescore
  35. 2026-06-24 01:44 UTCGHSA enrichment
  36. 2026-06-23 21:33 UTCEPSS rescore
  37. 2026-06-23 21:33 UTCEPSS rescore
  38. 2026-06-22 14:25 UTCEPSS rescore
  39. 2026-06-22 14:25 UTCEPSS rescore
  40. 2026-06-21 14:56 UTCEPSS rescore
  41. 2026-06-21 14:56 UTCEPSS rescore
  42. 2026-06-21 01:59 UTCEPSS rescore
  43. 2026-06-21 01:59 UTCEPSS rescore
  44. 2026-06-20 13:48 UTCGHSA enrichment
  45. 2026-06-19 19:26 UTCEPSS rescore
  46. 2026-06-19 19:26 UTCEPSS rescore
  47. 2026-06-18 17:52 UTCEPSS rescore
  48. 2026-06-18 17:52 UTCEPSS rescore
  49. 2026-06-18 16:54 UTCGHSA enrichment
  50. 2026-06-18 01:20 UTCGHSA enrichment
  51. 2026-06-17 17:53 UTCEPSS rescore
  52. 2026-06-17 13:41 UTCGHSA enrichment
  53. 2026-06-17 02:17 UTCGHSA enrichment
  54. 2026-06-16 17:53 UTCEPSS rescore
  55. 2026-06-16 14:54 UTCGHSA enrichment
  56. 2026-06-16 03:02 UTCGHSA enrichment
  57. 2026-06-15 17:49 UTCEPSS rescore
  58. 2026-06-15 17:49 UTCEPSS rescore
  59. 2026-06-15 15:38 UTCGHSA enrichment
  60. 2026-06-15 04:14 UTCGHSA enrichment
  61. 2026-06-14 23:18 UTCEPSS rescore
  62. 2026-06-14 16:48 UTCGHSA enrichment
  63. 2026-06-14 05:22 UTCGHSA enrichment
  64. 2026-06-13 23:00 UTCEPSS rescore
  65. 2026-06-13 17:58 UTCGHSA enrichment
  66. 2026-06-13 06:15 UTCGHSA enrichment
  67. 2026-06-12 23:12 UTCEPSS rescore
  68. 2026-06-12 23:12 UTCEPSS rescore
  69. 2026-06-12 18:46 UTCGHSA enrichment
  70. 2026-06-12 07:23 UTCGHSA enrichment
  71. 2026-06-11 19:59 UTCGHSA enrichment
  72. 2026-06-11 14:00 UTCEPSS rescore
  73. 2026-06-11 08:36 UTCGHSA enrichment
  74. 2026-06-10 22:19 UTCEPSS rescore
  75. 2026-06-10 21:13 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-49139?
CVE-2026-49139 is a high vulnerability published on June 1, 2026. 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…
When was CVE-2026-49139 disclosed?
CVE-2026-49139 was first published in the National Vulnerability Database on June 1, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49139 actively exploited?
CVE-2026-49139 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 69.2% of all scored CVEs.
What is the CVSS score of CVE-2026-49139?
CVE-2026-49139 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-49139?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49139, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-49139

Explore →

Is Your Infrastructure Affected by CVE-2026-49139?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs