An issue in ralphje Signify before v.0.9.2 allows a remote attacker to escalate privileges via the signed_data.py and the context.py components
CVE-2025-70887
This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(medium)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity88% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 28%
- KEV
- Not listed
Published
March 25, 2026
Last Modified
June 17, 2026
Advisory Details (5)
Auto-updated Aug 2, 2026bug: Validation weaknesses concerning X.509 Key Usage · Issue #60 · ralphje/signify · GitHub
https://github.com/ralphje/signify/issues/60commit 64f21c0cc06c (ralphje/signify)
Fix landed in ralphje/signify commit 64f21c0cc06c — awaiting tagged release
https://github.com/ralphje/signify/commit/64f21c0cc06cea0536370686ca3ba7a01e4adaa82.11
Patch available: mtrojnar/osslsigncode 2.11
https://github.com/mtrojnar/osslsigncode/releases/tag/2.11Add keyUsage digitalSignature validation for signer certificate
Patch available: mtrojnar/osslsigncode 2.11 (PR #477 merged 2025-12-31)
https://github.com/mtrojnar/osslsigncode/pull/477bug: Validation weaknesses concerning X.509 Key Usage · Issue #475 · mtrojnar/osslsigncode · GitHub
https://github.com/mtrojnar/osslsigncode/issues/475Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| signify | 0.1.1 ... 0.9.1 (19 versions) | 0.9.2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 25× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 14:07 UTCEPSS rescore
- 2026-09-16 05:14 UTCEPSS rescore
- 2026-09-15 03:10 UTCEPSS rescore
- 2026-09-13 16:46 UTCEPSS rescore
- 2026-09-12 15:00 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-11 09:36 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:00 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-02 14:01 UTCOSV refresh
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-08-30 01:21 UTCEPSS rescore
- 2026-08-28 21:40 UTCEPSS rescore
- 2026-08-27 14:24 UTCEPSS rescore
- 2026-08-26 14:45 UTCEPSS rescore
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-24 14:16 UTCEPSS rescore
- 2026-08-23 00:18 UTCEPSS rescore
- 2026-08-21 23:48 UTCEPSS rescore
Show 35 moreShow fewer
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:46 UTCEPSS rescore
- 2026-08-16 14:55 UTCEPSS rescore
- 2026-08-16 10:14 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 06:32 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 20:48 UTCEG score recompute
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 20:53 UTCEG score recompute
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 03:56 UTCEG score recompute
- 2026-08-10 23:59 UTCEPSS rescore
- 2026-08-09 19:10 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 06:07 UTCEG score recompute
- 2026-08-08 16:36 UTCEPSS rescore
- 2026-08-07 16:27 UTCEG score recompute
- 2026-08-07 16:27 UTCEPSS rescore
- 2026-08-06 18:50 UTCEG score recompute
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 00:57 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 10:37 UTCEPSS rescore
- 2026-08-03 23:40 UTCEG score recompute
- 2026-08-03 10:35 UTCEPSS rescore
- 2026-08-02 15:28 UTCEG score recompute
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 04:15 UTCEPSS rescore
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-27 14:23 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-269
Frequently asked(5)
What is CVE-2025-70887?
When was CVE-2025-70887 disclosed?
Is CVE-2025-70887 actively exploited?
What is the CVSS score of CVE-2025-70887?
How do I remediate CVE-2025-70887?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-70887
Is Your Infrastructure Affected by CVE-2025-70887?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.