Skip to main content
VulnerabilityPublished Updated

CVE-2024-36536: fabedge · Incorrect Authorization

Affects fabedgeSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jul 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubfabedge/fabedgepkg:github/fabedge/fabedgeOther threatsAffected
  • =0.8.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-36536, organizations should immediately audit and restrict permissions associated with service account tokens in fabedge deployments, ensuring the principle of least privilege is enforced. Network segmentation should be applied to limit access to fabedge management interfaces and service accounts. Monitoring and logging of service account token usage can help detect anomalous activities indicative of exploitation attempts. Until an official patch is released, consider disabling or isolating vulnerable fabedge instances where feasible. Employ strong identity and access management (IAM) policies, including rotating service account credentials regularly and using short-lived tokens if supported. Organizations should stay informed through fabedge vendor communications and apply security updates promptly once available. Additionally, implementing runtime security controls and endpoint detection can help identify and respond to exploitation attempts quickly.

Description

Insecure permissions in fabedge v0.8.1 allows attackers to access sensitive data and escalate privileges by obtaining the service account's token.

References

Community reviews

Loading reviews…