PatchTheCVECVE-2019-14367: Slack-Chat through 1.5.5 leaks a Slack Access Token in source code
CVE-2019-14367 is a high-severity flaw (CVSS 7.5) affecting slack-chat. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Slack-Chat through 1.5.5 leaks a Slack Access Token in source code. An attacker can obtain a lot of information about the victim's Slack (channels, members, etc.).
Why this priority
- High severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.5 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 1.2% (top 32%) |
| CISA exploited list | No |
| Weakness | CWE-200 |
| Published | 2019-11-12 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2019-14367?
slack-chat: upgrade to newer than 1.5.5. Exact commands for each OS are on this page.
Is CVE-2019-14367 being exploited?
CVE-2019-14367 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2019-14367 affect?
CVE-2019-14367 affects slack-chat. Severity is high (CVSS 7.5). Slack-Chat through 1.5.5 leaks a Slack Access Token in source code. An attacker can obtain a lot of information about the victim's Slack (channels, members, etc.).
How urgent is CVE-2019-14367?
Priority 48/100. High severity; Remotely exploitable, no login, no user action