[Azure Linux Security Servicing Account (azurelinux-security)]

Auto Patch influxdb for CVE-2026-97045, CVE-2026-78661, CVE-2026-116591, CVE-2026-116587, CVE-2026-116586, CVE-2026-116585, CVE-2026-114456.

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

CVE-2026-116587 : Single Patch Backporter Pipeline Run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1244434&view=results
CVE-2026-116585 : Single Patch Backporter Pipeline Run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1244435&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 influxdb for CVE-2026-97045 (MEDIUM), CVE-2026-78661 (MEDIUM), CVE-2026-116591 (MEDIUM), CVE-2026-116587 (MEDIUM), CVE-2026-116586 (MEDIUM), CVE-2026-116585 (MEDIUM), CVE-2026-114456 (MEDIUM).

Change Log

• CVE-2026-97045
• CVE-2026-78661
• CVE-2026-116591
• CVE-2026-116587
• CVE-2026-116586
• CVE-2026-116585
• CVE-2026-114456

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-97045
• https://nvd.nist.gov/vuln/detail/CVE-2026-78661
• https://nvd.nist.gov/vuln/detail/CVE-2026-116591
• https://nvd.nist.gov/vuln/detail/CVE-2026-116587
• https://nvd.nist.gov/vuln/detail/CVE-2026-116586
• https://nvd.nist.gov/vuln/detail/CVE-2026-116585
• https://nvd.nist.gov/vuln/detail/CVE-2026-114456

Test Methodology

• Pipeline build id: Buddy Build URL
• Pipeline build id: Buddy Build URL

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Aditya Singh (v-aaditya)]

Build Failure Analysis -
Issue -

1. Buddy Build failed as the patch file for CVE-2026-116585 contained \t characters in the new test file which was not present in current AZL source.
2. Since influxdb has 2 copies of vendor module go-jose, CVE-2026-116585, CVE-2026-116586, CVE-2026-116587 patched only 1 copy of go-jose leaving the other copy as vulnerable..

Fix -

1. As the current AZL source of vendor module go-jose in influxdb did not have any test files, therefore removed the changes made in test files.
2. Patched both the copies of go-jose for CVE-2026-116585, CVE-2026-116586, CVE-2026-116587.

CVE Analysis:

1. After modification, all the patches completely match with their respective upstream patches except the changes in test files are not included as they are not present.
2. All the patch files include upstream patch references.
3. pTest has passed.
4. PR has security tag.
5. Re-triggered Buddy Build and it has passed.

[Kanishk Bansal (Kanishk-Bansal)]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.

[Kanishk Bansal (Kanishk-Bansal)]

Patch Analysis (CVE-2026-97045, CVE-2026-78661, CVE-2026-116591, CVE-2026-116585, CVE-2026-116586 Matches Upstream, CVE-2026-116587 the backport differs only in square/go-jose: error prefixes for the vendored go-jose.v2 copy)
in the previous runs python-pbr/virtualenv was failing which is not related to this PRs and was failing previously also, hence re triggered the CIs

• Buddy Build
• patch applied during the build (check rpm.log)
• patch include an upstream reference
• PR has security tag

[Aditya Singh (v-aaditya)]

Updated patch for CVE-2026-114456 -

Issues -

1. 355 added lines contain literal \t text instead of real tabs. Go rejects them with illegal character U+005C, so the patch doesn't compile.
2. Calls httpResponse.Header.Set(...) on a bytes.Buffer, which has no Header field, which also causes compile error further.
3. The AI patch rewrites far more in the original file than it needs to; by removing around 189 LOC.

Fix -

1. Replaced \t text with real tabs.
2. After modification the patch builds a proper http.Header and writes it through writeExternalBrowserResponse.
3. After modification the patch keeps the original code, such as the legacy token parser and comments, wherever possible.

Re-triggered Buddy Build and it has passed.