CVE-2026-49139

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.0 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% 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: cna:vulncheck, epss
Trending — 4 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
32%
KEV
Not listed

Published

June 1, 2026

Last Modified

July 28, 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 7× in last 7d / 34× 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 239 total refreshes for this CVE.

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

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 28, 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 68.3% of all scored CVEs.
What is the CVSS score of CVE-2026-49139?
CVE-2026-49139 has a CVSS v4.0 base score of 7.0 (CNA self-assessment; NVD's own analysis pending).
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