CVE-2022-34927: MilkyTracker v1.03.00 was discovered to contain a stack overflow via the component LoaderXM::load

This month

HIGH 7.8DOWNGRADE

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

MilkyTracker v1.03.00 was discovered to contain a stack overflow via the component LoaderXM::load. This vulnerability is triggered when the program is supplied a crafted XM module file.

Why this priority

High severity
Public exploit reference

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

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.4% (top 67%)
CISA exploited list	No
Weakness	CWE-787
Published	2022-08-03
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: milkytracker project

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

Am I affected?

Timeline

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

milkytracker project milkytracker DOWNGRADE

Affected: 1.03.00

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.03.00

1. Check installed version

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

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

apt-cache madison milkytracker sudo apt install milkytracker=<VERSION_BEFORE_1.03.00> sudo apt-mark hold milkytracker

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

dnf --showduplicates list milkytracker sudo dnf downgrade milkytracker-<VERSION_BEFORE_1.03.00> sudo dnf versionlock add milkytracker

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

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

Is CVE-2022-34927 being exploited?

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

CVE-2022-34927 affects milkytracker. Severity is high (CVSS 7.8). MilkyTracker v1.03.00 was discovered to contain a stack overflow via the component LoaderXM::load. This vulnerability is triggered when the program is supplied a crafted XM module file.

How urgent is CVE-2022-34927?

Priority 40/100. High severity; Public exploit reference

Related CVEs

CVE-2020-15569 MEDIUM 5.5 UPGRADE MITIGATE PlayerGeneric.cpp in MilkyTracker through 1.02.00 has a use-after-free in the PlayerGeneric destructor.

References

← Back to latest CVEs