home.social

#patchrelease — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #patchrelease, aggregated by home.social.

  1. 🛠️ Home Assistant 2025.9.4 is out. A small weekend patch and the final one in the 2025.9 cycle.

    Next up: beta for 2025.10 starts next week.

    Have a great weekend and happy automating 🤖

    #HomeAssistant #SmartHome #OpenSource #PatchRelease #Automation

  2. 🛠️ Home Assistant 2025.9.4 is out. A small weekend patch and the final one in the 2025.9 cycle.

    Next up: beta for 2025.10 starts next week.

    Have a great weekend and happy automating 🤖

  3. 🛠️ Home Assistant 2025.9.4 is out. A small weekend patch and the final one in the 2025.9 cycle.

    Next up: beta for 2025.10 starts next week.

    Have a great weekend and happy automating 🤖

    #HomeAssistant #SmartHome #OpenSource #PatchRelease #Automation

  4. 🛠️ Home Assistant 2025.9.4 is out. A small weekend patch and the final one in the 2025.9 cycle.

    Next up: beta for 2025.10 starts next week.

    Have a great weekend and happy automating 🤖

    #HomeAssistant #SmartHome #OpenSource #PatchRelease #Automation

  5. 🛠️ Home Assistant 2025.9.4 is out. A small weekend patch and the final one in the 2025.9 cycle.

    Next up: beta for 2025.10 starts next week.

    Have a great weekend and happy automating 🤖

    #HomeAssistant #SmartHome #OpenSource #PatchRelease #Automation

  6. 🆕 We released OpenProject 15.4.2 today. This release contains several bug fixes and we highly recommend updating to the newest version.

    See our release notes for details: openproject.org/docs/release-n

    #OpenProject #ProjectManagement #Release #OpenSource #PatchRelease

  7. 🆕 We released OpenProject 15.4.2 today. This release contains several bug fixes and we highly recommend updating to the newest version.

    See our release notes for details: openproject.org/docs/release-n

  8. 🆕 We released OpenProject 15.4.2 today. This release contains several bug fixes and we highly recommend updating to the newest version.

    See our release notes for details: openproject.org/docs/release-n

    #OpenProject #ProjectManagement #Release #OpenSource #PatchRelease

  9. 🆕 We released OpenProject 15.4.2 today. This release contains several bug fixes and we highly recommend updating to the newest version.

    See our release notes for details: openproject.org/docs/release-n

    #OpenProject #ProjectManagement #Release #OpenSource #PatchRelease

  10. 🆕 We released OpenProject 15.4.2 today. This release contains several bug fixes and we highly recommend updating to the newest version.

    See our release notes for details: openproject.org/docs/release-n

    #OpenProject #ProjectManagement #Release #OpenSource #PatchRelease

  11. 🆕 We just released OpenProject 15.4.1. The release contains several bug fixes and we highly recommend updating to the newest version.

    See our release notes for details: openproject.org/docs/release-n

    #OpenProject #ProjectManagement #Release #OpenSource #PatchRelease

  12. 🆕 We just released OpenProject 15.4.1. The release contains several bug fixes and we highly recommend updating to the newest version.

    See our release notes for details: openproject.org/docs/release-n

  13. 🆕 We just released OpenProject 15.4.1. The release contains several bug fixes and we highly recommend updating to the newest version.

    See our release notes for details: openproject.org/docs/release-n

    #OpenProject #ProjectManagement #Release #OpenSource #PatchRelease

  14. 🆕 We just released OpenProject 15.4.1. The release contains several bug fixes and we highly recommend updating to the newest version.

    See our release notes for details: openproject.org/docs/release-n

    #OpenProject #ProjectManagement #Release #OpenSource #PatchRelease

  15. 🆕 We just released OpenProject 15.4.1. The release contains several bug fixes and we highly recommend updating to the newest version.

    See our release notes for details: openproject.org/docs/release-n

    #OpenProject #ProjectManagement #Release #OpenSource #PatchRelease

  16. GitLab Security Update: Critical Patches Released

    Date: April 24, 2024
    CVE: Multiple (e.g., CVE-2024-4024, CVE-2024-2434)
    Vulnerability Type: Authentication Issues, Path Traversal, DoS, Information Disclosure
    CWE: [[CWE-287]], [[CWE-22]], [[CWE-400]], [[CWE-284]]
    Sources: GitLab Security Release

    Issue Summary

    GitLab has released critical security updates (16.11.1, 16.10.4, 16.9.6) addressing multiple high and medium severity vulnerabilities across various versions. The identified issues include authentication bypass, path traversal, and denial of service attacks.

    Technical Key findings

    Key vulnerabilities allow unauthorized account access, server file reading, and service disruption due to inadequate input validation and authentication checks.

    Table of security fixes

    |Title|Severity|
    |---|---|
    |GitLab account takeover, under certain conditions, when using Bitbucket as an OAuth provider|High|
    |Path Traversal leads to DoS and Restricted File Read|High|
    |Unauthenticated ReDoS in FileFinder when using wildcard filters in project file search|High|
    |Personal Access Token scopes not honoured by GraphQL subscriptions|Medium|
    |Domain based restrictions bypass using a crafted email address|Medium|

    Vulnerable products

    • GitLab Community Edition (CE)
    • GitLab Enterprise Edition (EE)all versions starting from 7.8 before 16.9.6all versions starting from 16.10 before 16.10.4 all versions starting from 16.11 before 16.11.1.

    Impact assessment

    Exploits could lead to account takeovers, unauthorized access to sensitive data, and significant service disruptions affecting availability and integrity.

    Patches or workaround

    Upgrading to the latest versions (16.11.1, 16.10.4, 16.9.6) is strongly recommended as they contain necessary security fixes. To update GitLab, see the Update page.

    Tags

    #GitLab #CVE-2024-4024 #CVE-2024-2434 #AuthenticationBypass #PathTraversal #DenialOfService #PatchRelease

  17. GitLab Security Update: Critical Patches Released

    Date: April 24, 2024
    CVE: Multiple (e.g., CVE-2024-4024, CVE-2024-2434)
    Vulnerability Type: Authentication Issues, Path Traversal, DoS, Information Disclosure
    CWE: [[CWE-287]], [[CWE-22]], [[CWE-400]], [[CWE-284]]
    Sources: GitLab Security Release

    Issue Summary

    GitLab has released critical security updates (16.11.1, 16.10.4, 16.9.6) addressing multiple high and medium severity vulnerabilities across various versions. The identified issues include authentication bypass, path traversal, and denial of service attacks.

    Technical Key findings

    Key vulnerabilities allow unauthorized account access, server file reading, and service disruption due to inadequate input validation and authentication checks.

    Table of security fixes

    |Title|Severity|
    |---|---|
    |GitLab account takeover, under certain conditions, when using Bitbucket as an OAuth provider|High|
    |Path Traversal leads to DoS and Restricted File Read|High|
    |Unauthenticated ReDoS in FileFinder when using wildcard filters in project file search|High|
    |Personal Access Token scopes not honoured by GraphQL subscriptions|Medium|
    |Domain based restrictions bypass using a crafted email address|Medium|

    Vulnerable products

    • GitLab Community Edition (CE)
    • GitLab Enterprise Edition (EE)all versions starting from 7.8 before 16.9.6all versions starting from 16.10 before 16.10.4 all versions starting from 16.11 before 16.11.1.

    Impact assessment

    Exploits could lead to account takeovers, unauthorized access to sensitive data, and significant service disruptions affecting availability and integrity.

    Patches or workaround

    Upgrading to the latest versions (16.11.1, 16.10.4, 16.9.6) is strongly recommended as they contain necessary security fixes. To update GitLab, see the Update page.

    Tags

    #GitLab #CVE-2024-4024 #CVE-2024-2434 #AuthenticationBypass #PathTraversal #DenialOfService #PatchRelease

  18. GitLab Security Update: Critical Patches Released

    Date: April 24, 2024
    CVE: Multiple (e.g., CVE-2024-4024, CVE-2024-2434)
    Vulnerability Type: Authentication Issues, Path Traversal, DoS, Information Disclosure
    CWE: [[CWE-287]], [[CWE-22]], [[CWE-400]], [[CWE-284]]
    Sources: GitLab Security Release

    Issue Summary

    GitLab has released critical security updates (16.11.1, 16.10.4, 16.9.6) addressing multiple high and medium severity vulnerabilities across various versions. The identified issues include authentication bypass, path traversal, and denial of service attacks.

    Technical Key findings

    Key vulnerabilities allow unauthorized account access, server file reading, and service disruption due to inadequate input validation and authentication checks.

    Table of security fixes

    |Title|Severity|
    |---|---|
    |GitLab account takeover, under certain conditions, when using Bitbucket as an OAuth provider|High|
    |Path Traversal leads to DoS and Restricted File Read|High|
    |Unauthenticated ReDoS in FileFinder when using wildcard filters in project file search|High|
    |Personal Access Token scopes not honoured by GraphQL subscriptions|Medium|
    |Domain based restrictions bypass using a crafted email address|Medium|

    Vulnerable products

    • GitLab Community Edition (CE)
    • GitLab Enterprise Edition (EE)all versions starting from 7.8 before 16.9.6all versions starting from 16.10 before 16.10.4 all versions starting from 16.11 before 16.11.1.

    Impact assessment

    Exploits could lead to account takeovers, unauthorized access to sensitive data, and significant service disruptions affecting availability and integrity.

    Patches or workaround

    Upgrading to the latest versions (16.11.1, 16.10.4, 16.9.6) is strongly recommended as they contain necessary security fixes. To update GitLab, see the Update page.

    Tags

    #GitLab #CVE-2024-4024 #CVE-2024-2434 #AuthenticationBypass #PathTraversal #DenialOfService #PatchRelease

  19. GitLab Security Update: Critical Patches Released

    Date: April 24, 2024
    CVE: Multiple (e.g., CVE-2024-4024, CVE-2024-2434)
    Vulnerability Type: Authentication Issues, Path Traversal, DoS, Information Disclosure
    CWE: [[CWE-287]], [[CWE-22]], [[CWE-400]], [[CWE-284]]
    Sources: GitLab Security Release

    Issue Summary

    GitLab has released critical security updates (16.11.1, 16.10.4, 16.9.6) addressing multiple high and medium severity vulnerabilities across various versions. The identified issues include authentication bypass, path traversal, and denial of service attacks.

    Technical Key findings

    Key vulnerabilities allow unauthorized account access, server file reading, and service disruption due to inadequate input validation and authentication checks.

    Table of security fixes

    |Title|Severity|
    |---|---|
    |GitLab account takeover, under certain conditions, when using Bitbucket as an OAuth provider|High|
    |Path Traversal leads to DoS and Restricted File Read|High|
    |Unauthenticated ReDoS in FileFinder when using wildcard filters in project file search|High|
    |Personal Access Token scopes not honoured by GraphQL subscriptions|Medium|
    |Domain based restrictions bypass using a crafted email address|Medium|

    Vulnerable products

    • GitLab Community Edition (CE)
    • GitLab Enterprise Edition (EE)all versions starting from 7.8 before 16.9.6all versions starting from 16.10 before 16.10.4 all versions starting from 16.11 before 16.11.1.

    Impact assessment

    Exploits could lead to account takeovers, unauthorized access to sensitive data, and significant service disruptions affecting availability and integrity.

    Patches or workaround

    Upgrading to the latest versions (16.11.1, 16.10.4, 16.9.6) is strongly recommended as they contain necessary security fixes. To update GitLab, see the Update page.

    Tags

    #GitLab #CVE-2024-4024 #CVE-2024-2434 #AuthenticationBypass #PathTraversal #DenialOfService #PatchRelease

  20. GitLab Security Update: Critical Patches Released

    Date: April 24, 2024
    CVE: Multiple (e.g., CVE-2024-4024, CVE-2024-2434)
    Vulnerability Type: Authentication Issues, Path Traversal, DoS, Information Disclosure
    CWE: [[CWE-287]], [[CWE-22]], [[CWE-400]], [[CWE-284]]
    Sources: GitLab Security Release

    Issue Summary

    GitLab has released critical security updates (16.11.1, 16.10.4, 16.9.6) addressing multiple high and medium severity vulnerabilities across various versions. The identified issues include authentication bypass, path traversal, and denial of service attacks.

    Technical Key findings

    Key vulnerabilities allow unauthorized account access, server file reading, and service disruption due to inadequate input validation and authentication checks.

    Table of security fixes

    |Title|Severity|
    |---|---|
    |GitLab account takeover, under certain conditions, when using Bitbucket as an OAuth provider|High|
    |Path Traversal leads to DoS and Restricted File Read|High|
    |Unauthenticated ReDoS in FileFinder when using wildcard filters in project file search|High|
    |Personal Access Token scopes not honoured by GraphQL subscriptions|Medium|
    |Domain based restrictions bypass using a crafted email address|Medium|

    Vulnerable products

    • GitLab Community Edition (CE)
    • GitLab Enterprise Edition (EE)all versions starting from 7.8 before 16.9.6all versions starting from 16.10 before 16.10.4 all versions starting from 16.11 before 16.11.1.

    Impact assessment

    Exploits could lead to account takeovers, unauthorized access to sensitive data, and significant service disruptions affecting availability and integrity.

    Patches or workaround

    Upgrading to the latest versions (16.11.1, 16.10.4, 16.9.6) is strongly recommended as they contain necessary security fixes. To update GitLab, see the Update page.

    Tags

    #GitLab #CVE-2024-4024 #CVE-2024-2434 #AuthenticationBypass #PathTraversal #DenialOfService #PatchRelease

  21. Latest release 1.10.1

    We’re happy to announce the release of a new patch for the Crystal 1.10 series, which comes with three bugfixes. To view full statistics and changes brought in by the patch release, please visit crystal-lang.org/2023/10/13/1.. Installation instructions can be found at crystal-lang.org/install/.

    We are grateful to everyone who contributed for their work in enhancing the language.

    Happy Crystalising🙂 !
    #CrystalLang #Patchrelease

  22. Latest release 1.10.1

    We’re happy to announce the release of a new patch for the Crystal 1.10 series, which comes with three bugfixes. To view full statistics and changes brought in by the patch release, please visit crystal-lang.org/2023/10/13/1.. Installation instructions can be found at crystal-lang.org/install/.

    We are grateful to everyone who contributed for their work in enhancing the language.

    Happy Crystalising🙂 !

  23. Latest release 1.10.1

    We’re happy to announce the release of a new patch for the Crystal 1.10 series, which comes with three bugfixes. To view full statistics and changes brought in by the patch release, please visit crystal-lang.org/2023/10/13/1.. Installation instructions can be found at crystal-lang.org/install/.

    We are grateful to everyone who contributed for their work in enhancing the language.

    Happy Crystalising🙂 !
    #CrystalLang #Patchrelease

  24. Latest release 1.10.1

    We’re happy to announce the release of a new patch for the Crystal 1.10 series, which comes with three bugfixes. To view full statistics and changes brought in by the patch release, please visit crystal-lang.org/2023/10/13/1.. Installation instructions can be found at crystal-lang.org/install/.

    We are grateful to everyone who contributed for their work in enhancing the language.

    Happy Crystalising🙂 !
    #CrystalLang #Patchrelease

  25. Latest release 1.10.1

    We’re happy to announce the release of a new patch for the Crystal 1.10 series, which comes with three bugfixes. To view full statistics and changes brought in by the patch release, please visit crystal-lang.org/2023/10/13/1.. Installation instructions can be found at crystal-lang.org/install/.

    We are grateful to everyone who contributed for their work in enhancing the language.

    Happy Crystalising🙂 !
    #CrystalLang #Patchrelease