[AutoPR- Security] Patch ldns for CVE-2026-10846 [HIGH]

[azurelinux-security]

Auto Patch ldns for CVE-2026-10846.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1136624&view=results

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

What does the PR accomplish, why was it needed?

• Auto Patch ldns for CVE-2026-10846 (HIGH).

Change Log

• CVE-2026-10846

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-10846

Test Methodology

• Pipeline build id: Buddy Build URL

[kgodara912]

Buddy build

[kgodara912]

Backport Adaptation Notes

Backport of NLnetLabs/ldns@9ea51a6 to ldns 1.8.3.

What was adapted:

1. Enum insertion point changed — New status codes (LDNS_STATUS_ID_DID_NOT_MATCH, LDNS_STATUS_QDCOUNT_MUST_BE_ONE, LDNS_STATUS_QUERY_DID_NOT_MATCH) are appended after LDNS_STATUS_INVALID_SVCPARAM_VALUE (last entry in 1.8.3) instead of after LDNS_STATUS_EQUAL_RR which only exists in newer versions.

2. TXID matching hunk omitted — The original commit changes an existing TXID check (printf("wrong TXID!\n") → LDNS_STATUS_ID_DID_NOT_MATCH) and updates a return path (LDNS_STATUS_ERR → status ? status : LDNS_STATUS_ERR). This entire code path does not exist in 1.8.3, so the hunk is not applicable.

3. LDNS_STATUS_ID_DID_NOT_MATCH defined but unused — The enum value is still added for ABI consistency with upstream, but no code references it in 1.8.3 since the TXID verification logic was introduced in a later release.

What was preserved as-is:

• QDCOUNT validation at ldns_send_buffer() entry (rejects queries without exactly one question)
• Response question section matching before returning result (verifies response matches query)
• All three new error codes and their human-readable strings in error.c

[CBL-Mariner-Bot]

Auto cherry-pick results:

• 3.0-dev ✅ -> [AUTO-CHERRYPICK] [AutoPR- Security] Patch ldns for CVE-2026-10846 [HIGH] - branch 3.0-dev #17708

Auto cherry-pick pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1137749&view=results