Ory logo
Legal documents

Ory Vulnerability (CVE) Remediation SLA

Read Ory's Vulnerability (CVE) Remediation SLA detailing timelines and scope for fixing confirmed security issues in Ory Network, OEL, and CSL.

Last updated Nov 13, 2026

1. Purpose

This document outlines Ory's commitment to the timely remediation of security vulnerabilities in the Ory Network and related products for Enterprise customers.

2. Scope

This policy applies to Ory Network Services and Ory Enterprise License Containers.

3. Technical Vulnerability Management

Ory employs a comprehensive vulnerability management process to promptly identify, evaluate, and remediate security vulnerabilities. We use multiple methods to obtain information about technical vulnerabilities:

  • Automated vulnerability scanning
  • Regular penetration testing
  • Security researcher submissions
  • Threat intelligence feeds
  • Vendor security advisories

Automated vulnerability scans are executed after each commit/container build and continuously for the current images. Penetration tests of the Ory components and Ory Network are performed annually. Additional penetration tests are performed following significant changes to production systems.

Upon detection, Ory's security and engineering teams evaluate each vulnerability based on its severity, exploitability, and potential impact to determine appropriate remediation timeframes.

4. Vulnerability Assessment

Ory follows industry-standard practices for vulnerability assessment. The assigned severity level may differ from automatically generated ratings based on Ory's internal knowledge of system architecture and real-world exploitability.

5. Remediation Timeframes

Ory is committed to remediating identified vulnerabilities according to the following timeframes:

Severity LevelDescriptionRemediation Timeframe
CriticalVulnerabilities that could be easily exploited and lead to system compromise, significant data loss, or service disruption14 days
HighVulnerabilities that are harder to exploit but could still lead to system compromise30 days
MediumVulnerabilities that are limited in scope or difficult to exploit90 days
LowVulnerabilities with minimal impact or requiring complex exploitation180 days
InformationalItems that pose minimal risk but are noted for best practicesAs needed

6. Exceptions Process

In situations where a vulnerability cannot be remediated within the standard timeframe, Ory implements a formal exceptions process that requires:

  1. Documentation of the exception
  2. Risk assessment and business justification
  3. Development of a risk treatment plan with compensating controls
  4. Defined timeline for ultimate remediation
  5. Approval by security leadership

7. Monitoring and Reporting

Ory continuously monitors the status of vulnerability remediation efforts to ensure compliance with this policy. Enterprise customers may request vulnerability status reports as part of regular security reviews.

8. Additional Security Measures

Beyond vulnerability management, Ory implements multiple layers of security controls:

  • Regular security testing and code reviews
  • Network segmentation and firewalls
  • Encryption of data in transit and at rest
  • Multi-factor authentication
  • Comprehensive logging and monitoring
  • Incident response capabilities

9. Commitment to Security

Ory is committed to maintaining the security, confidentiality, and availability of our services. This policy represents our ongoing dedication to addressing security vulnerabilities promptly and effectively to protect our enterprise customers' data and systems.