-
Notifications
You must be signed in to change notification settings - Fork 680
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add release note for Solr8 version upgrade #9365
Changes from 1 commit
700b31a
1c0dfa0
63c2627
dd66212
a947273
9fe6b80
dbcf3dc
45be0b7
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,13 @@ | ||
--- | ||
title: "Upgraded Solr8 version to address recent Security Vulnerabilities" | ||
title: "Upgraded Solr8 version to address recent security vulnerabilities" | ||
published_date: "2025-01-07" | ||
categories: [security] | ||
--- | ||
|
||
We are pleased to announce the release of an upgraded Solr8 version that addresses the latest CVE affecting prior Solr8 releases. This update includes critical security patches to safeguard against potential exploits. As always, we remain committed to delivering robust solutions that keep your data secure and operations running smoothly. | ||
We are pleased to announce the release of an upgraded Solr8 version that resolves recently reported security vulnerabilities affecting prior Solr8 releases. This update includes critical security patches to safeguard against potential exploits. As always, we remain committed to delivering robust solutions that keep your data secure and operations running smoothly. | ||
|
||
### What's new? ### | ||
* **Security vulnerability fixes:** This release addresses the latest CVE impacting previous versions of Solr8. | ||
* **Critical security patches:** Key patches have been applied to mitigate potential exploits and enhance overall system security. | ||
|
||
We recommend upgrading to this version promptly to maintain a secure and stable environment. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @azharone is this correct? I didn't think user action is required. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That is correct—no action is required. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @IngridKwok Reviewed and made some changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of "This update includes critical security patches to safeguard against potential exploits."
I would suggest "This update addresses a vulnerability identified in CVE-XXXXX, although this vulnerability did not impact the security of the Pantheon platform directly."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@christianyates Makes sense! Made the change.