CVE-2024-36536: Insecure permissions in fabedge v0.8.1 allows attackers to access sensitive data and escalate privileges by ob

This month

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2024-36536 is a critical-severity flaw (CVSS 9.8) affecting fabedge. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

Critical severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 59%)
CISA exploited list	No
Weakness	CWE-863
Published	2024-07-24
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: fabedge

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-07-24 19:15 UTCPublished CVE record published
2026-06-17 07:36 UTCUpdated Record last modified

fabedge fabedge DOWNGRADE

Affected: 0.8.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.8.1

1. Check installed version

apt-cache policy fabedge || rpm -q fabedge || fabedge --version

2. No fixed release: DOWNGRADE to a release before 0.8.1 (Debian / Ubuntu)

apt-cache madison fabedge sudo apt install fabedge=<VERSION_BEFORE_0.8.1> sudo apt-mark hold fabedge

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list fabedge sudo dnf downgrade fabedge-<VERSION_BEFORE_0.8.1> sudo dnf versionlock add fabedge

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
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-2024-36536?

fabedge: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-36536 being exploited?

CVE-2024-36536 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-2024-36536 affect?

CVE-2024-36536 affects fabedge. Severity is critical (CVSS 9.8). Insecure permissions in fabedge v0.8.1 allows attackers to access sensitive data and escalate privileges by obtaining the service account's token.

How urgent is CVE-2024-36536?

Priority 50/100. Critical severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs