Skip to content

Fix the two private security advisories before the release #208

Closed

Description

@ingvarch

Two reports from the security review of 2026-11-09 are private advisories, as SECURITY.md asks. Only the maintainer can open them:

Each advisory has the places in the code, the fix and the tests to write first. The fixes are made in the private fork of the advisory or in a pull request that does not describe the problem, and each advisory is published with the release that has its fix.

This issue is closed when both are fixed and released.

Activity

  1. added this to the v0.19.0 milestone on Nov 9, 2026
  2. added
    priority: highFix first: loses data, breaks a cluster or crashes urga
    securitySecurity hardening or a vulnerability fix
    on Nov 9, 2026
  3. ingvarch commented on Nov 10, 2026

    @ingvarch
    OwnerAuthor

    Both fixes are in v0.19.0 (#221, #222), and both advisories are published: GHSA-9x2m-75cc-22gg and GHSA-w7qh-qfh4-4v6m.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: highFix first: loses data, breaks a cluster or crashes urgasecuritySecurity hardening or a vulnerability fix

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions