OSSEVA FOR POSTGRESQL

Your Postgres version is EOL. Your data isn't going anywhere.

OSSeva ships CVE patches for PostgreSQL 11, 12, and 13 past their community end-of-life dates — with migration planning, configuration audits, and audit-ready compliance documentation.

Book a PostgreSQL DiscoverySee version coverage ↓

Why now

PostgreSQL 11 EOL: November 2023

PostgreSQL 11 passed community EOL in November 2023. 12 follows in November 2024, 13 in November 2025. Unpatched CVEs in your primary datastore are a direct compliance failure.

Migration is costly and risky

Major-version Postgres migrations touch every application query. A rushed migration introduces regression risk. OSSeva gives you time to do the migration right while keeping your current version patched.

Oracle exit customers need a landing zone

Enterprises migrating off Oracle Database frequently land on PostgreSQL. Those migrations take 12–24 months. OSSeva supports the Postgres version you landed on while your team finishes the migration.

Versions covered

All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.

VersionStatusActive CVEs
11.xExtendedClean
12.xExtendedClean
13.xExtendedClean
14.xCurrentClean
15.xCurrentClean
16.xCurrentClean

What you get

Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.

OSSeva Patch

CVE remediation for EOL PostgreSQL versions.

  • Quarterly security patches for covered versions
  • Signed packages for RPM / DEB / tarball
  • Extension compatibility validation
  • Vulnerability disclosure notifications
  • Migration planning
Get started →
Most popular

OSSeva Assure

Patches plus migration roadmap and compliance documentation.

  • Everything in Patch
  • Major-version migration planning
  • Performance and vacuum configuration audit
  • Compliance attestation package
  • Oracle-to-Postgres migration design
  • 24/7 managed operations
Get started →

OSSeva Operate

Full DBA-level managed operations for your Postgres fleet.

  • Everything in Assure
  • 24/7 replication and failover monitoring
  • Automated VACUUM and analyze tuning
  • 15-minute P1 incident response SLA
  • Point-in-time recovery testing
  • Quarterly capacity reviews
Get started →

All tiers priced per cluster/application — not per core. Contact for pricing →

How it installs

OSSeva artifacts arrive via your existing package infrastructure. Pull the patched version the same way you pull upstream today — just from the OSSeva registry.

APT — OSSeva PostgreSQL repositorybash
curl -fsSL https://packages.osseva.io/gpg | sudo gpg --dearmor -o /usr/share/keyrings/osseva.gpg
echo "deb [signed-by=/usr/share/keyrings/osseva.gpg] https://packages.osseva.io/postgresql $(lsb_release -cs) main" \
  | sudo tee /etc/apt/sources.list.d/osseva-postgresql.list
sudo apt update && sudo apt install postgresql-13-osseva

Compliance library

📄SOC 2 Type II Attestation
Request →
📄Sample Audit Narrative
Request →
📄Pen-Test Report Summary
Request →
📄HIPAA Technical Safeguard Matrix
Request →

Frequently asked questions

Which versions of RabbitMQ are past community end-of-life?

RabbitMQ 3.8.x, 3.9.x, 3.10.x, 3.11.x, and 3.12.x have all reached community EOL — meaning no further security patches or CVE fixes are released by the RabbitMQ maintainers for those versions. RabbitMQ 3.13.x reached EOL in late 2024. OSSeva delivers backported CVE patches for 3.11 through 3.13.

Which PostgreSQL versions are no longer receiving community security patches?

PostgreSQL 9.6 through 13 have all reached community EOL. PostgreSQL 11 reached EOL November 2023, PostgreSQL 12 reached EOL November 2024, and PostgreSQL 13 reaches EOL November 2025. OSSeva provides extended security patching for PostgreSQL 11, 12, and 13 for teams that cannot immediately migrate to PG 14 or later.

Is Spring Framework 5.3.x still supported?

Spring Framework 5.3.x reached its community OSS EOL on December 31, 2024. Broadcom's commercial support for Spring 5.3.x is also no longer available under standard terms. OSSeva delivers backported CVE patches for Spring Framework 5.3.x and Spring Boot 2.7.x under our extended lifecycle support program.

Which versions of Apache Kafka are EOL?

Apache Kafka versions 2.x and 3.0 through 3.4 are past their community supported window, meaning no further patch releases. Kafka 3.5 and 3.6 have reached or are approaching EOL. OSSeva supports Kafka 2.8 through 3.5 with backported security patches and compliance documentation.

What happened to Redis licensing? Can I still use Redis for free?

In March 2024, Redis Ltd. changed the Redis license from BSD-3-Clause to the Business Source License (BSL 1.1), which restricts use in competing database products. The Valkey project (a Linux Foundation fork) continues under BSD-3-Clause. OSSeva maintains BSD-licensed, CVE-patched builds of Redis 6.2 and 7.0 for enterprises that need verifiable open-source licensing alongside security coverage.

Is Node.js 18 still receiving security patches?

Node.js 18 (LTS 'Hydrogen') reached its end-of-life date in April 2025 and no longer receives security releases from the Node.js project. OSSeva delivers CVE patches for Node.js 18 for enterprise teams that have not yet migrated to Node.js 20 or 22.

Is Apache Tomcat 8.5 still supported?

Apache Tomcat 8.5 reached its community EOL in March 2024. OSSeva provides extended security patching for Tomcat 8.5.x for teams running Java EE 7 workloads that cannot immediately migrate to Tomcat 9.0 or 10.1.

What .NET versions does OSSeva support?

.NET 6 reached Microsoft end-of-support in November 2024. .NET 7 reached EOL in May 2024. OSSeva delivers CVE patches for .NET 6 and .NET 7 for teams that have not yet migrated to .NET 8 (LTS, supported through November 2026).

Ready to get PostgreSQL patched and supported?

Start with a 45-minute discovery call. We confirm your version coverage, scope the engagement, and have you onboarded within your first quarter.

Book PostgreSQL Discovery