PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-82263 logto-io CVE debrief

CVE-2026-82263 is a high-severity vulnerability in Logto, a software identity and access management solution. The vulnerability is caused by a server-side request forgery (SSRF) issue in the OIDC SSO connector creation endpoint, which allows tenant administrators with Management API credentials to supply arbitrary internal URLs and trigger HTTP GET requests to private network services. The response content is returned in API responses, potentially exposing sensitive information.

Vendor
logto-io
Product
logto
CVSS
HIGH 8.2
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-28
Original CVE updated
2026-09-08
Advisory published
2026-08-28
Advisory updated
2026-09-08

Who should care

Defenders responsible for managing Logto deployments, particularly those with tenant administrators who have Management API credentials, should assess their exposure to this vulnerability and prioritize patching or mitigation efforts.

Why it matters

CVE-2026-82263 is a high-severity SSRF vulnerability in Logto that allows tenant administrators to trigger HTTP GET requests to private network services, potentially exposing sensitive information. Defenders should prioritize verifying affected versions and applying patches or mitigations to prevent exploitation.

  • Potential exposure of sensitive information through API responses
  • Possible disruption of private network services due to triggered HTTP GET requests
  • Need for verification of affected versions and patching or mitigation efforts
  • Potential impact on confidentiality and integrity of sensitive data

Technical summary

The vulnerability is caused by a lack of validation in the issuer URL parameter of the OIDC SSO connector creation endpoint. This allows tenant administrators with Management API credentials to supply arbitrary internal URLs and trigger HTTP GET requests to private network services. The response content is returned in API responses, potentially exposing sensitive information. Affected product deployments should be verified, and patches or mitigations should be applied to prevent exploitation. The vulnerability has been confirmed to exist in Logto version 1.42.0 and earlier, and further verification is needed to determine the full scope of affected versions and potential impact.

Defensive priority

Defenders should prioritize verifying the affected versions of Logto in their environment and applying the necessary patches or mitigations to prevent exploitation.

Recommended defensive actions

  • Verify the version of Logto in use and check if it is affected by the vulnerability
  • Apply patches or mitigations provided by the vendor to fix the vulnerability
  • Monitor API responses for potential sensitive information exposure
  • Restrict Management API credentials to prevent unauthorized access
  • 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 vulnerability is confirmed to exist in Logto version 1.42.0 and earlier. The CVE record and NVD entry provide details on the vulnerability, but further verification is needed to determine the full scope of affected versions and potential impact.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-82263 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-82263 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

    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.