Security Resilience

CVE-2025-70887

Ralphje Signify ≤ 0.9.2

Published
25 March 2026
Modified
01 April 2026
Patch / advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0035 27th percentile
Risk Priority 63 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-70887 is a high-severity Improper Privilege Management (CWE-269) vulnerability in Ralphje Signify. Its CVSS base score is 8.8 (High).

Operationally, ranked at the 27th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-2 (Account Management) and AC-24 (Access Control Decisions) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-70887 is a privilege escalation vulnerability in ralphje's Signify tool prior to version 0.9.2, published on 2026-03-25. The flaw resides in the signed_data.py and context.py components and is classified under CWE-269 (Improper Privilege Management). It carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), indicating high severity due to network accessibility, low attack complexity, and significant impacts on confidentiality, integrity, and availability.

A remote attacker possessing low privileges (PR:L) can exploit the vulnerability without user interaction. Exploitation occurs over the network with low complexity, enabling privilege escalation on affected systems running vulnerable versions of Signify.

Mitigation is addressed through updates in the ralphje/signify repository, including the fix in commit 64f21c0cc06cea0536370686ca3ba7a01e4adaa8 and discussion in issue #60; users should upgrade to version 0.9.2 or later. Related concerns in the osslsigncode project are covered in issue #475, pull request #477, and release 2.11.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-9068Shared CWE-269
CVE-2026-28889Shared CWE-269
CVE-2024-29052Shared CWE-269
CVE-2023-32196Shared CWE-269
CVE-2026-60938Shared CWE-269
CVE-2026-100586Shared CWE-269
CVE-2023-23429Shared CWE-269
CVE-2024-37455Shared CWE-269
CVE-2026-6226Shared CWE-269
CVE-2025-7341Shared CWE-269

Affected Assets

ralphje
signify
≤ 0.9.2

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Account management directly governs assignment and tracking of privileges so proper implementation stops the weakness from being introduced.

Requiring explicit access-control decisions ensures privileges are evaluated rather than assumed or omitted.

Access enforcement applies the correct privilege checks at every request, structurally preventing unintended spheres of control.

Separation of duties constrains how privileges may be assigned, reducing the chance of overly broad actor control.

Least privilege is the direct countermeasure to improper privilege management; implementing it eliminates the root cause.

Binding security attributes to subjects/objects supplies the mechanism needed to track and enforce privileges correctly.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.5.15 directly mandates determining access requirements, defining/enforcing topic-specific access control policy, assigning rights/restrictions by entity/role, consistency with classification, need-to-know, privileged access restrictions, segregation, formal authorization, and dynamic rules — which stops most improper privilege management from being exploitable; bounded remainder is flawed implementation of those rules (e.g. incorrect mapping or enforcement bugs).

blocks

A.5.18 directly governs the provisioning, review, modification and timely revocation of access rights (including for role changes, termination and privilege levels), which stops most improper privilege spheres from being exploitable even if the assignment flaw exists; the bounded remainder is flaws in the underlying enforcement mechanism itself (e.g. AC-3/A.8.3)

blocks

A.8.2 directly controls the identification, allocation, review, expiry, temporary use, and separation of privileged rights per policy, which prevents most improper privilege management (CWE-269) by design; the bounded remainder is flawed tracking/checking logic inside the product's own enforcement code (the AC-3 slice of 269).

blocks

A.8.3 directly restricts access per policies (config mechanisms, per-user/group rights, isolation, dynamic techniques, auth/credential enforcement), which stops exploitation of most improper privilege management cases even if the assignment/tracking flaw remains; named remainder exists for non-access-control privilege errors (e.g. pure assignment bugs outside enforcement).

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

References