CVE-2022-40299: In Singular before 4.3.1, a predictable /tmp pathname is used (e.g., by sdb.cc), which allows local users to g

Q: How do I fix CVE-2022-40299?

singular: upgrade to 4.3.1. Exact commands for each OS are on this page.

Q: Is CVE-2022-40299 being exploited?

CVE-2022-40299 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-40299 affect?

CVE-2022-40299 affects singular. Severity is high (CVSS 7.8). In Singular before 4.3.1, a predictable /tmp pathname is used (e.g., by sdb.cc), which allows local users to gain the privileges of other users via a procedure in a file under /tmp. NOTE: this CVE Record is about sdb.cc and similar files in

Q: How urgent is CVE-2022-40299?

Priority 39/100. High severity; Public exploit reference

Routine

HIGH 7.8UPGRADE

CVE-2022-40299 is a high-severity flaw (CVSS 7.8) affecting singular. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In Singular before 4.3.1, a predictable /tmp pathname is used (e.g., by sdb.cc), which allows local users to gain the privileges of other users via a procedure in a file under /tmp. NOTE: this CVE Record is about sdb.cc and similar files in the Singular interface that have predictable /tmp pathnames; this CVE Record is not about the lack of a safe temporary-file creation capability in the Singular language.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 73%)
CISA exploited list	No
Weakness	CWE-330
Published	2022-09-09
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: singular

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

Am I affected?

Timeline

2022-09-09 01:15 UTCPublished CVE record published
2026-06-17 05:01 UTCUpdated Record last modified

singular singular UPGRADE

Affected: < 4.3.1

Fixed in: 4.3.1

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 4.3.1 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade singular

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

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-2022-40299?

singular: upgrade to 4.3.1. Exact commands for each OS are on this page.

Is CVE-2022-40299 being exploited?

CVE-2022-40299 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-2022-40299 affect?

CVE-2022-40299 affects singular. Severity is high (CVSS 7.8). In Singular before 4.3.1, a predictable /tmp pathname is used (e.g., by sdb.cc), which allows local users to gain the privileges of other users via a procedure in a file under /tmp. NOTE: this CVE Record is about sdb.cc and similar files in

How urgent is CVE-2022-40299?

Priority 39/100. High severity; Public exploit reference

References

← Back to latest CVEs