CVE-2021-41418: AriaNg v0.1.0~v1.2.2 is affected by an incorrect access control vulnerability through not authenticating visit

This week

CRITICAL 9.8REMOTEUPGRADE

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

AriaNg v0.1.0~v1.2.2 is affected by an incorrect access control vulnerability through not authenticating visitors' access rights.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.0% (top 37%)
CISA exploited list	No
Weakness	CWE-306
Published	2022-06-15
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: ariang project

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

Am I affected?

Timeline

2022-06-15 20:15 UTCPublished CVE record published
2026-06-17 04:08 UTCUpdated Record last modified

ariang project ariang UPGRADE

Affected: >= 0.1.0 and <= 1.2.2

Fixed in: newer than 1.2.2

Safe to downgrade to: a release before 0.1.0

1. Check installed version

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

2. UPGRADE to newer than 1.2.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade ariang

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade ariang

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 0.1.0 (Debian / Ubuntu)

apt-cache madison ariang sudo apt install ariang=<VERSION_BEFORE_0.1.0> sudo apt-mark hold ariang

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list ariang sudo dnf downgrade ariang-<VERSION_BEFORE_0.1.0> sudo dnf versionlock add ariang

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-2021-41418?

ariang: upgrade to newer than 1.2.2. Exact commands for each OS are on this page.

Is CVE-2021-41418 being exploited?

CVE-2021-41418 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-2021-41418 affect?

CVE-2021-41418 affects ariang. Severity is critical (CVSS 9.8). AriaNg v0.1.0~v1.2.2 is affected by an incorrect access control vulnerability through not authenticating visitors' access rights.

How urgent is CVE-2021-41418?

Priority 60/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs