The GeoServer community has readied the following CVE vulnerabilities for public disclosure.

The release announcements listed above have been updated.

Free software is a participation sport - to create a patch for a prior release volunteer with community development.

Q: How often should I upgrade GeoServer?

GeoServer operates with a time boxed release cycle, maintaining “stable” and “maintenance” releases, over the course of a year.

  • Upgrade GeoServer twice a year as new stable releases are made.

  • Once the release you are using has entered “maintenance” it is a good idea to upgrade (before the release is no longer supported).

  • GeoServer security policy provides one year of support. You may also contact our service providers for extended support beyond this timeframe.

Q: Notification of security vulnerabilities?

Stay up to date:

  1. Please monitor release announcements for the heading “Security Considerations”.

    Security Considerations

    This release addresses several security vulnerabilities, and is a recommended upgrade for production systems.

    You can review the release announcement, and decide to update.

  2. When everyone has had an opportunity to update the details of the vulnerability are announced.

    Security Considerations

    This release addresses several security vulnerabilities, and is a recommended upgrade for production systems.

    • CVE-2024-29198 Unauthenticated SSRF via TestWfsPost (Moderate)
  3. Review the full vulnerability to learn more:

    CVE Report

  4. Scanning tools also have access to this information when the report is published:

    CVE Scan Results

Q: Notification of security reports?

As incoming security reports contain sensitive information they are only shared with representatives of the geoserver-security email list.

Participation in geoserver-security, like commit access, is volunteer based and reflects trust.

Please review GeoServer Security Policy if you are in a position to help out.