Certbot 5.10.0 fixes a local webroot authenticator flaw (GHSA-9qv6-9g6h-3x7x); no CVE assigned yet
Identifiers: GHSA-9qv6-9g6h-3x7x
- Published
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
Summary
The Certbot project released 5.10.0 on 10 November 2026 with the fix, and published advisory GHSA-9qv6-9g6h-3x7x on 20 November 2026 (updated the same day). No CVE is assigned in the vendor notice at the time of checking. The vendor describes a local vulnerability in the webroot authenticator: a lower-privileged local account that can write to the webroot, or to a relevant parent directory or path component, may cause unauthorized ownership or permission changes while a higher-privileged Certbot creates challenge directories. The advisory scenario is Certbot run as root. Upstream Certbot before 5.10.0 is affected; 5.10.0 and later are fixed.
Impact
The risk is that a lower-privileged local account causes ownership or permission changes on files handled by the higher-privileged Certbot process. The advisory reports a laboratory demonstration of such a file permission or ownership change only; it does not establish a complete privilege escalation or real-world exploitation, and it describes escalation as a conditional possibility. The preconditions are local: an account on the same host with write access to the challenge path or a relevant component of it. That is not the same as any remote website visitor being able to exploit the flaw. The advisory does not describe a flaw in the other authenticators or any general exposure of certificate private keys.
Who is affected
Upstream Certbot <5.10.0 is affected and >=5.10.0 is fixed. It matters where the webroot authenticator is used, Certbot runs with higher privileges than some local accounts, and one of those accounts can write to the webroot or a relevant parent directory or path component. Shared hosting, where one privileged renewal job serves many customer directories, is one example of such a layout; single-tenant servers with separate deploy or application accounts can also qualify. Distribution packages, containers and hosting panels that bundle Certbot deliver fixes on their own schedule and may backport under older version numbers, so their own advisory or changelog is the evidence that counts.
Products and versions
| Products and versions | Affected | Fixed |
|---|---|---|
| Certbot webroot authenticator | <5.10.0 | >=5.10.0 |
Exploitation evidence
Exploitation not established. The Certbot advisory reports a laboratory demonstration of a file permission or ownership change under the stated local conditions and does not establish exploitation in the wild. The preconditions are local and differ from what a remote visitor could do. Absence of a report is not confirmation that no misuse has occurred.
Actions
- Establish who runs certificate issuance and renewals on each host, which authenticator is configured, and which local accounts can write to the webroot challenge path or its parent directories.
- Upgrade the exact package, container image or automation that performs issuance and renewal to 5.10.0 or later, rather than only the copy on a workstation.
- For Certbot delivered by a distribution or panel, check the vendor's own backport statement before treating an older version number as unfixed or fixed.
- After upgrading, confirm the version of the runner that the scheduler actually invokes, then validate renewals following the vendor's prescribed maintenance and safe validation guidance. Do not switch authenticators or issue real certificates as part of this check.
- If the package cannot be updated immediately, have the host administrator review which lower-privileged accounts can write to the challenge path and restrict that access while keeping renewals working.
Unknowns
- No CVE identifier is assigned in the vendor notice yet; one may follow.
- Whether a given host meets the conditions depends on its account layout and who runs renewals, which must be checked locally.
- Backport status for individual distributions and panels is not confirmed here.
- The advisory reports a file permission or ownership change in a laboratory setting; whether a full escalation is achievable on any specific configuration is not established.
Sources
- Certbot project https://github.com/certbot/certbot/security/advisories/GHSA-9qv6-9g6h-3x7x
- Certbot project https://github.com/certbot/certbot/releases/tag/v5.10.0
Change history
- — Published: 20 November 2026: record created for Certbot advisory GHSA-9qv6-9g6h-3x7x, a local webroot authenticator flaw fixed in release 5.10.0 of 10 November 2026, with no CVE assigned and no established exploitation.