PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-92792 OpenNHP CVE debrief

CVE-2026-92792 is a high-severity vulnerability in OpenNHP through 1.0.2, allowing attackers to bypass attestation verification. The vulnerability exists because OpenNHP selects its trusted-execution attestation verifier based on attacker-supplied evidence containing a test_purpose key, causing the FallbackVerifier to execute unconditionally. This could lead to unauthorized access if attackers provide enrolled measure and serial number pairs from the allowlist.

Vendor
OpenNHP
Product
Unknown
CVSS
HIGH 8.7
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-16
Original CVE updated
2026-09-19
Advisory published
2026-09-16
Advisory updated
2026-09-19

Who should care

Defenders responsible for OpenNHP deployments should assess their exposure and prioritize verification and patching. This includes reviewing system configurations, monitoring for suspicious activity, and applying security updates as they become available.

Why it matters

CVE-2026-92792 is a high-severity vulnerability in OpenNHP that allows attackers to bypass attestation verification, potentially leading to unauthorized access. Defenders should prioritize verifying the presence of this vulnerability in their OpenNHP deployments and apply patches or mitigations as available. The exact scope of affected versions and systems requires further verification from official sources.

  • Verify attestation verification mechanisms in OpenNHP deployments
  • Assess the risk of unauthorized access due to bypassed verification
  • Monitor OpenNHP systems for potential exploitation attempts
  • Prioritize patching or mitigating the vulnerability in OpenNHP systems

Technical summary

The vulnerability exists in OpenNHP through version 1.0.2. Attackers can bypass attestation verification by including a test_purpose key in the evidence and providing enrolled measure and serial number pairs from the allowlist. This could lead to unauthorized access. Defenders should prioritize verifying the presence of this vulnerability in their OpenNHP deployments and apply patches or mitigations as available. The exact scope of affected versions and systems requires further verification from official sources. OpenNHP deployments should be reviewed for potential exposure, and security updates should be applied as they become available.

Defensive priority

Defenders should prioritize verifying the presence of this vulnerability in their OpenNHP deployments and apply patches or mitigations as available.

Recommended defensive actions

  • Verify the presence of OpenNHP in your environment and assess the version
  • Review and apply patches or updates for OpenNHP as available
  • Monitor OpenNHP systems for suspicious activity
  • Consider implementing additional security controls for OpenNHP deployments
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description and CVSS score. However, the exact scope of affected versions and systems requires further verification from official sources.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-92792 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-92792

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-92792 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-92792

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.