Skip to content
Fencer Intel
high 7.5

CVE-2019-9768 in the critical feed json

Thinkst Canarytokens through commit hash 4e89ee0 (2019-03-01) relies on limited variation in size, metadata, and timestamp, which makes it…

published 7y ago modified 4mo ago also EUVD-2019-19130

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
11.7%
EPSS 11.7% chance of exploitation in 30 days, percentile 96%
public exploits
1
Exploit-DB

Summary

Thinkst Canarytokens through commit hash 4e89ee0 (2019-03-01) relies on limited variation in size, metadata, and timestamp, which makes it easier for attackers to estimate whether a Word document contains a token.

Is CVE-2019-9768 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. First public exploit (EDB-46589)

Exploit prediction

11.68% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-46589 Canarytokens 2019-03-01 - Detection Bypass dos, 2019-03-21
  • packetstormsecurity.com http://packetstormsecurity.com/files/152182/Canarytokens-2019-03-01-Detection-Bypass.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.