2 hours ago
Our production Postgres service is Online. A “Security patch scheduled: Postgres” warning created on August 20 is still marked ACTIVE, although the service auto-updated successfully on August 22 during the stated maintenance window.
Could Railway confirm whether that auto-update applied the fixes for all CVEs listed in the warning? If the fixes were applied, should the warning be resolved, and why does it remain ACTIVE? If further action is required from us, please let us know.
I can provide the notification and deployment identifiers if needed.
1 Replies
Status changed to Awaiting Railway Response Railway • about 2 hours ago
an hour ago
Your August 22 update addressed all 12 CVEs listed in the warning. The warning stayed active because a bug prevented the older notification from clearing after the update. We’ve now resolved it, and no further action is needed from you.
Status changed to Awaiting User Response Railway • about 1 hour ago