github-actions[bot] commented on PR #5364: URL: https://github.com/apache/solr/pull/5364#issuecomment-6998029962
**Automated PR readiness judgements** (LLM-generated; may be wrong; not updated on later pushes). - ⚠️ [Jira issue in title](https://github.com/apache/solr/blob/main/CONTRIBUTING.md) **— missing**: This is a security mitigation for a critical CVE (CVE-2026-114938) that changes the default behavior of the Docker image and provides a new configuration option in solr.in.sh, which is a user-visible change warranting a Jira issue and changelog entry. - ⚠️ [Changelog](https://github.com/apache/solr/blob/main/dev-docs/changelog.adoc#_changelog_types_reference) **— differs from the entry** (suggest type: fixed; PR has type: security): The change mitigates a critical Remote Code Execution vulnerability (CVE-2026-114938) by disabling a vulnerable JDK intrinsic, which is a security fix with user-visible implications (performance impact of disabling intrinsic, security posture). - ⚠️ [Reference Guide update](https://github.com/apache/solr/tree/main/solr/solr-ref-guide) **— missing** (confidence: medium): The PR introduces a new JVM option (`-XX:-UseBASE64Intrinsics`) as a recommended mitigation in `solr.in.sh` and enables it by default in the Docker image. This user-facing configuration change and its rationale should be documented in the Reference Guide (e.g., in the Security or Installation sections) to inform operators. - ⚠️ [Upgrade notes](https://github.com/apache/solr/tree/main/solr/solr-ref-guide/modules/upgrade-notes/pages) **— missing**: The Docker image now enables `-XX:-UseBASE64Intrinsics` by default, which is a change in default behavior for users upgrading the Docker image. While likely a performance-neutral or minor regression, it is a behavioral change that operators should be aware of, especially if they rely on the intrinsic for performance or have specific JVM tuning. - ✅ Tests: not needed <!-- The changes are limited to configuration files (`solr.in.sh`, `solr.in.cmd`) and a Dockerfile template. There is no production Java logic changed, and testing JVM flags or Dockerfile generation is typically handled by build/CI processes rather than unit tests. --> <!-- Assessed commit df02c476251731aad334877063de5d74feb223ce --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
