Skip to content
Fencer Intel
critical 9.8

CVE-2020-36911 in the critical feed json

Covenant 0.5 - Remote Code Execution (RCE)

published 9mo ago modified 4mo ago also EUVD-2026-2654

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
12.3%
EPSS 12.3% chance of exploitation in 30 days, percentile 96%
public exploits
0
none known

Summary

Covenant 0.1.3 - 0.5 contains a remote code execution vulnerability that allows attackers to craft malicious JWT tokens with administrative privileges. Attackers can generate forged tokens with admin roles and upload custom DLL payloads to execute arbitrary commands on the target system.

Patch / fix

Is CVE-2020-36911 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

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
total
Assessed
9mo ago

Exploit prediction

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

Exploits and checks

  • exploit-db.com https://www.exploit-db.com/exploits/51141 referenced PoC, tagged "exploit" by a source, unverified
  • web.archive.org https://web.archive.org/web/20201101052547/https://blog.null.farm/hunting-the-hunters referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/Zeop-CyberSec/covenant_rce/blob/master/covenant_jwt_rce.rb referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 9.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 4.0 9.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected products

  • Cobbr Covenant

Classification

Weakness
  • CWE-798 Use of Hard-coded Credentials

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.