spomky-labs/pki-framework

Releases

1. ▸▾1.6.312 Sept 2026

   Total pull requests resolved: 2

   Release Notes for 1.6.3

   1.6.x bugfix release (patch)

   1.6.3

   • Total issues resolved: 0
   • Total pull requests resolved: 2
   • Total contributors: 1

   bug

   • 118: fix(x509): drop the dead index increments flagged by PHPStan thanks to @Spomky

   dependencies

   • 117: fix(composer): allow brick/math 1.0 thanks to @Spomky

   Open source →
2. ▸▾1.6.28 Sept 2026

   This release fixes 27 security advisories — 1 critical, 14 high, 8 medium and 4 low. Every one of them affects <= 1.6.1 and is patched in 1.6.2 ; the

   Release Notes for 1.6.2

   1.6.x bugfix release (patch)

   Security

   This release fixes 27 security advisories — 1 critical, 14 high, 8 medium and 4 low. Every one of them affects <= 1.6.1 and is patched in 1.6.2; the 1.0.x through 1.5.x lines are end of life and receive no fix, so users on those lines must upgrade to 1.6.2.

   Anyone validating certification paths, name constraints or attribute certificates with this library should upgrade.

   Critical

   • GHSA-3p3r-m556-g5px — Name constraints are never enforced during certification path validation

   High

   • GHSA-2rhj-2r69-j232 — Distinguished name comparison is defeated by the ASN.1 string type and by invisible characters, and made to collide by lossy transcoding
   • GHSA-5474-45mw-c3xq — TBSCertificate::fromCSR() copies attacker-controlled extensions, allowing a requester to obtain a CA certificate
   • GHSA-6chf-2x6r-fjhg — iPAddress GeneralNames silently encode a different address, turning an IPv6 name constraint into a wildcard IPv4 constraint
   • GHSA-85g4-f9rx-c6ww — Attribute certificate signatures are exempt from the configured signature algorithm and RSA key size policy
   • GHSA-9hcj-84c7-2pj8 — A second [3] extensions element in tbsCertificate silently replaces the first, hiding basicConstraints and keyUsage
   • GHSA-c67f-8q64-6hxh — Missing loop detection in CertificationPathBuilder allows memory exhaustion with two crafted certificates
   • GHSA-gjx8-fvx6-qg7q — KeyUsage and reasonFlags bits are read from the wrong end of an over-long BIT STRING, so keyCertSign can be forged
   • GHSA-mh5j-7xj5-9h45 — Name constraints are evaded by names the matcher does not canonicalise: a trailing dot, and URIs PHP parses differently from browsers
   • GHSA-mxjh-6r54-88x9 — CertificationPath::validate() silently treats the first certificate of the chain as the trust anchor
   • GHSA-rfxw-c9pp-xvfw — The MAX_PATHS bound never fires when no path reaches a trust anchor, so 7 KB of certificates costs minutes of CPU
   • GHSA-v473-mx2x-xqpv — A few kilobytes of crafted DER cost minutes of CPU: unbounded quadratic accumulation in tag numbers, OID sub-identifiers and REAL mantissas
   • GHSA-v76j-9ghr-85fr — Unrecognized critical certificate extensions are silently ignored during path validation
   • GHSA-vw7q-hxmh-m835 — X.509 v1/v2 certificates are accepted as intermediate CAs without any basicConstraints check
   • GHSA-xjj7-24gw-437v — Unbounded recursion in the ASN.1/DER decoder causes a stack-exhaustion crash (SIGSEGV)

   Moderate

   • GHSA-34rx-vp5j-q2wr — The certificate policy tree grows multiplicatively per certificate, so a signed chain from a delegated sub-CA exhausts memory
   • GHSA-5gp6-jr6q-ffx7 — MD4, MD5 and SHA-1 certificate signatures are accepted with no way to restrict the algorithm set
   • GHSA-6pj8-5pjp-gj6w — An unsupported critical extension in an attribute certificate is ignored, so the issuer's restrictions are silently discarded
   • GHSA-894f-9q28-7w2x — Comparing a multi-valued RDN re-encodes and re-parses both names, so a 14 KB certificate costs 0.3 s per name comparison
   • GHSA-f28f-xc9q-m482 — Signature is verified over a re-encoded TBSCertificate, making certificates malleable
   • GHSA-jj8p-rwmj-6rjj — Malformed ASN.1 input raises a TypeError that escapes catch(Exception), crashing the caller
   • GHSA-mx53-vr97-rxr2 — ECDSA signature values are re-encoded before verification, so one certificate has an unlimited supply of accepted byte encodings
   • GHSA-x673-qv99-7268 — PEM_REGEX backtracks cubically, so 4 KB of text costs more CPU than parsing thousands of real certificates

   Low

   • GHSA-6q28-45jq-2628 — No syntax validation on dNSName / rfc822Name allows embedded NUL bytes in subjectAltName
   • GHSA-8qrh-8g3j-pxvv — Certificate serial numbers default to 0 and withRandomSerialNumber() yields under 64 bits of entropy
   • GHSA-j49g-8r6c-p7w2 — UTCTime two-digit years 50-69 are decoded with the wrong century, so expired certificates can be seen as valid
   • GHSA-wc4q-rp39-hwpf — Duplicate certificate extensions are silently merged, last occurrence wins

   1.6.2

   • Total issues resolved: 0
   • Total pull requests resolved: 3
   • Total contributors: 1

   bug

   • 114: fix(x509): accept a critical subjectAltName during path validation thanks to @Spomky
   • 113: fix(x509): report an uncomparable name as a path validation or building failure thanks to @Spomky
   • 112: Address the open hardening issues thanks to @Spomky