Repository navigation
Correct Log4j entry in Automate 4.13.535 release notes - #4778
Merged
Merged
Conversation
The bundled log4j-core is 2.17.1-tuxcare.4 (TuxCare backport), not 2.25.4. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: iamazzeez <aazeez@progress.com>
✅ Deploy Preview for chef-web-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
iamazzeez
added
the
ai-assisted
iamazzeez
requested review from
Dmaddu,
IanMadd,
Jayamathans12 and
punitmundra
October 27, 2026 06:57
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: iamazzeez <aazeez@progress.com>
Collaborator
|
@IanMadd kindly merge this PR |
Signed-off-by: Ian Maddaus <ian.maddaus@progress.com>
IanMadd
approved these changes
Oct 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Corrects the Log4j entry in the Chef Automate 4.13.535 release notes. It said the bundled Log4j Core was "upgraded to 2.25.4", but 4.13.535 ships
log4j-core-2.17.1-tuxcare.4.jarin bothos/libandos/performance-analyzer-rca/libofchef/automate-opensearch/1.3.20/20261012054213. This is TuxCare's 2.17.1 build with the 2.25.4 fixes backported. The old wording led customers to expect a 2.25.4 jar (CHEF-34535).TuxCare VEX for
log4j-core 2.17.1-tuxcare.4marks CVE-2025-68161, CVE-2026-34477 and CVE-2026-34480 as resolved:https://security.tuxcare.com/vex/cyclonedx/els_lang_java/org.apache.logging.log4j/log4j-core/2.17.1-tuxcare.4/vex.json
Reviewers, please confirm: the same VEX marks CVE-2026-49844 as
exploitableon2.17.1-tuxcare.4. The line above this one claims that CVE was addressed. I left it unchanged here; please verify with TuxCare and correct it if needed.This work was completed with AI assistance following Progress AI policies.
Definition of Done
Release note accurately describes the shipped Log4j version.
Issues Resolved
CHEF-34535
Related PRs
#4773
Check List