How severe is CVE-2026-50612?

CVE-2026-50612 has a CVSS 4.0 base score of 9.4, rated critical severity.

Is CVE-2026-50612 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (41st percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-50612?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2026-50612 published?

CVE-2026-50612 was published on 2026-10-15.

CVE-2026-50612

CVE-2026-50612 is a critical-severity vulnerability with a CVSS 4.0 base score of 9.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-61.

Key facts

Severity: Critical (CVSS 4.0 base score 9.4)
EPSS exploit prediction: 0% (41st percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-61
Published: 2026-10-15
Last modified: 2026-10-15

Description

An unix symbolic link (symlink) following vulnerability has been reported to affect QuMagie. If a remote attacker gains a user account, they can then exploit the vulnerability to compromise the security of the system. We have already fixed the vulnerability in the following version: QuMagie 2.9.2 and later

Frequently asked questions

What is CVE-2026-50612?: An unix symbolic link (symlink) following vulnerability has been reported to affect QuMagie. If a remote attacker gains a user account, they can then exploit the vulnerability to compromise the security of the system. We have already fixed the vulnerability in the following version: QuMagie 2.9.2 and later
How severe is CVE-2026-50612?: CVE-2026-50612 has a CVSS 4.0 base score of 9.4, rated critical severity.
Is CVE-2026-50612 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (41st percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-50612?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2026-50612 published?: CVE-2026-50612 was published on 2026-10-15.

References

https://www.qnap.com/en/app_releasenotes/list.php?app_choose=qumagie

Other CWE-61 vulnerabilities

CVE-2026-34078 — Critical (CVSS 10.0): Flatpak is a Linux application sandboxing and distribution framework. Prior to 1.16.4, the Flatpak portal accepts paths…
CVE-2025-62596 — Critical (CVSS 10.0): Youki is a container runtime written in Rust. In versions 0.5.6 and below, youki’s apparmor handling performs…
CVE-2025-62161 — Critical (CVSS 10.0): Youki is a container runtime written in Rust. In versions 0.5.6 and below, the initial validation of the source…
CVE-2026-91099 — Critical (CVSS 9.8): HP has identified and remediated multiple externally reported vulnerabilities within HPLIP. The findings affect several…
CVE-2025-23394 — Critical (CVSS 9.8): A UNIX Symbolic Link (Symlink) Following vulnerability in openSUSE Tumbleweed cyrus-imapd allows escalation from cyrus…
CVE-2024-54661 — Critical (CVSS 9.8): readline.sh in socat before1.8.0.2 relies on the /tmp/$USER/stderr2 file.

Browse all CWE-61 vulnerabilities →