Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-3379: In lunary-ai/lunary versions 1.2.2 through 1.2.6, an incorrect authorization vulnerability allows unprivileged

42
This month
HIGH 8.1UPGRADE

CVE-2024-3379 is a high-severity flaw (CVSS 8.1) affecting lunary. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In lunary-ai/lunary versions 1.2.2 through 1.2.6, an incorrect authorization vulnerability allows unprivileged users to re-generate the private key for projects they do not have access to. Specifically, a user with a 'Member' role can issue a request to regenerate the private key of a project without having the necessary permissions or being assigned to that project. This issue was fixed in version 1.2.7.

Why this priority

  • High severity
  • Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score8.1 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.4% (top 66%)
CISA exploited listNo
WeaknessCWE-863
Published2024-11-14
Last modified2026-06-17
Publisher (CNA): huntr.dev · Vendor: lunary

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

lunary lunary UPGRADE
Affected: >= 1.2.2 and < 1.2.7
Fixed in: 1.2.7
Safe to downgrade to: a release before 1.2.2
1. Check installed version
apt-cache policy lunary || rpm -q lunary || lunary --version
2. UPGRADE to 1.2.7 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade lunary
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade lunary
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.2.2 (Debian / Ubuntu)
apt-cache madison lunary sudo apt install lunary=<VERSION_BEFORE_1.2.2> sudo apt-mark hold lunary
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list lunary sudo dnf downgrade lunary-<VERSION_BEFORE_1.2.2> sudo dnf versionlock add lunary
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-3379?

lunary: upgrade to 1.2.7. Exact commands for each OS are on this page.

Is CVE-2024-3379 being exploited?

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

CVE-2024-3379 affects lunary. Severity is high (CVSS 8.1). In lunary-ai/lunary versions 1.2.2 through 1.2.6, an incorrect authorization vulnerability allows unprivileged users to re-generate the private key for projects they do not have access to. Specifically, a user with a 'Member' role can issue

How urgent is CVE-2024-3379?

Priority 42/100. High severity; Public exploit reference

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.