Ubuntu Patches Ruby OpenID Server-Side Request Forgery

P2 — VALIDATE AND UPDATENot provided by the authority · Not provided by the authorityEXPLOITATION: NOT STATED

Quick Answer

Update the Ubuntu ruby-openid package and restart affected applications. Review network egress from OpenID consumers.

Confirm Scope And Apply The Supported Remediation

What to do now: Inventory Ubuntu suite, installed ruby-openid packages, repository origin, active consumers and owners. Match the installed suite and package to the official notice; assess upstream or bundled copies separately. Install the listed security packages through the supported Ubuntu repositories. Confirm required Ubuntu Pro, ESM or Legacy Support entitlements for older suites. Verify the loaded library and test valid and invalid authentication responses; retain application and outbound-request evidence.

Open the authoritative advisory

Last verified: 2026-11-13 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeRuby OpenID response verification on the Ubuntu releases listed in USN-9085-1
AdvisoryUSN-9085-1
CVECVE-2019-11027
Authoritative release date2026-11-12 — November 12, 2026 at 20:54:47 UTC, from the official Ubuntu security feed; the notice gives the same date.
Authority revision dateNo separate revision date is provided by the authority.
Affected versionsUbuntu ruby-openid packages on the suites listed in the fixed-version table, before their respective security updates. Applicability is package-, feature- and suite-specific.
Fixed version18.04 LTS: ruby-openid 2.7.0debian-1ubuntu0.18.04.1~esm1; 16.04 LTS: ruby-openid 2.7.0debian-1ubuntu0.16.04.1~esm1
CVSS base scoreNot provided by the authority
CVSS severityNot provided by the authority
Exploitation statusThe Ubuntu notice does not confirm exploitation in the wild.; no exploitation claim is inferred.

What Changed

An OpenID claimed-identifier URL is requested before response-signature verification, allowing server-side request forgery.

What To Validate Now

  1. Inventory. Inventory Ubuntu suite, installed ruby-openid packages, repository origin, active consumers and owners.
  2. Establish applicability. Match the installed suite and package to the official notice; assess upstream or bundled copies separately.
  3. Remediate. Install the listed security packages through the supported Ubuntu repositories. Confirm required Ubuntu Pro, ESM or Legacy Support entitlements for older suites.
  4. Validate. Verify the loaded library and test valid and invalid authentication responses; retain application and outbound-request evidence.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Bundled gems may differ from distribution packages. Apply the fix to the library actually used by the service.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.