InfiniteWP Client: weak NOSSL signing key

InfiniteWP Client

InfiniteWP Client has a weak NOSSL signing key that can be recovered in under 5 minutes.

Do this now

Read the report and check whether InfiniteWP Client affects you.

First seen: 6 Nov 2026
Last update: 6 Nov 2026, 19:18 UTC
Source: news

Check this repository for exposure to one security incident from pwned.coffee. Report first, change nothing until I say so.

## InfiniteWP Client: weak NOSSL signing key
Severity: unknown. Patch status: fix status unknown.
Affected: InfiniteWP Client

InfiniteWP Client has a weak NOSSL signing key that can be recovered in under 5 minutes.

## Steps
1. Search the repo, its CI and infra config for InfiniteWP Client. If present, report the version in use and whether it's affected.
2. No source names a fix yet; check the vendor advisory. Until one ships: restrict network access to it.

## Report
A table: file, product or package, version in use, affected yes/no, exact fix. Then anything a human has to check outside the repo.

If you have the pwned.coffee MCP server (https://pwned.coffee/mcp), call lookup_cve for the latest, and check_repo with this repo's lockfiles, Dockerfiles and workflows for a full receipt.
Sources: https://seclists.org/oss-sec/2026/q4/563
https://pwned.coffee/i/infinitewp-client-weak-nossl-signing-key

Receipt

Exploitation: No known exploitation
Score: No CVSS published yet: severity unknown.
Last checked: 7 Nov 2026, 18:18 UTC

Sources: KEV – CVE record – Vendor –

Sources

seclists.org: InfiniteWP Client: the NOSSL signing key has 31 bits of secret — recovered live in 291.9 seconds

Follow on X

Totalone coffee