CVE-2026-42002 Concurrency and locking defects in GSS-TSIG
Medium 5.9
Published
Updated
Check this codebase for CVE-2026-42002 and fix it if it is affected.
What it is: CVE-2026-42002 is a medium-severity vulnerability in PowerDNS Authoritative, published on 21 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-42002 in the wild and no public exploit code.
Affected product: PowerDNS Authoritative. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-42002/ (Markdown: https://insights.sbomify.com/CVE-2026-42002/index.md)
Concurrency defects in GSS-TSIG allow attackers to cause denial of service in PowerDNS Authoritative servers.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-42002?
CVE-2026-42002 is a medium-severity vulnerability in PowerDNS Authoritative, published on 21 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Concurrency and locking defects in GSS-TSIG
Weakness: CWE-364
Which versions are affected by CVE-2026-42002?
It affects 1 product.
Products include Powerdns Authoritative.
How do I fix CVE-2026-42002?
Apply the vendor's patch.
Is CVE-2026-42002 being exploited?
There is no known exploitation of CVE-2026-42002 in the wild and no public exploit code.
Other vulnerabilities in PowerDNS Authoritative
Sources
Also known as DEBIAN-CVE-2026-42002, GHSA-vx6m-m9qv-88q3, UBUNTU-CVE-2026-42002.