On this page (6 sections)
Ubuntu has published USN-9085-1 on 12 November 2026, covering the ruby-openid package. The notice says the library could be made to connect to arbitrary servers, which is a server-side request forgery (SSRF) problem referenced as CVE-2019-11027.
If you run a Ruby application on Ubuntu 16.04 LTS or 18.04 LTS that signs users in through OpenID, this is worth checking. Ubuntu says the fixed packages are available through Ubuntu Pro (ESM Apps), so a plain apt update on a system without Pro attached may not offer them.
What happened
According to Ubuntu, ruby-openid sent a request to the claimed identifier URL before verifying the signature of an OpenID response. Ubuntu says a remote attacker could possibly use this to perform server-side request forgery attacks. Ubuntu describes the library as a Ruby library for verifying and serving OpenID identities.
The notice is short. It gives no CVSS score, no attack complexity rating and no report of real-world exploitation. Only one publisher, Ubuntu itself, covers this story so far, so the sections below stick to what that notice says and clearly mark anything that is general background.
Why the order of operations matters
The key detail in Ubuntu's description is sequencing. The library made an outbound request to a URL taken from the OpenID response before it had checked whether that response was correctly signed. Signature verification exists to reject forged responses, so any network activity that happens ahead of it is activity triggered by data that has not yet been trusted.
Ubuntu does not spell out the exact conditions an attacker would need, so treat the following as general background on SSRF rather than a description of this specific bug: SSRF means an attacker causes a server to send requests to a destination the attacker influences, which can matter when that server can reach systems the attacker cannot.
What SSRF can lead to in practice
- Probing internal hosts and ports that are not exposed to the internet.
- Reaching cloud metadata endpoints or other internal services that trust requests from the server.
- Making your server's IP address the source of requests to third-party sites.
Who is affected
Ubuntu lists two releases and one package:
| Ubuntu release | Package | Fixed version |
|---|---|---|
| 18.04 LTS (bionic) | ruby-openid | 2.7.0debian-1ubuntu0.18.04.1~esm1 |
| 16.04 LTS (xenial) | ruby-openid | 2.7.0debian-1ubuntu0.16.04.1~esm1 |
Realistic exposure requires that the library is installed and that an application actually uses it to handle OpenID logins. A server with the package installed but no application calling it is much less likely to be at risk. Applications that bundle their own copy of the gem, for example through Bundler, are not updated by the system package, so check your Gemfile.lock as well.
How to check your exposure
This read-only command lists the installed ruby-openid package and its version on Debian or Ubuntu. An error saying no packages were found means the package is not installed from the system repositories.
dpkg -l ruby-openidCompare the version with the fixed versions in the table above. If your application uses Bundler, this command, run from the application directory, searches the lockfile for the gem and shows which version the app pins.
grep -n openid Gemfile.lockThis only shows the gem name and version in the lockfile. Whether a bundled version has the same flaw is not covered by the Ubuntu notice, so consult the gem's own release notes.
What to do now
- Run the dpkg check above on every Ubuntu 16.04 and 18.04 host that runs Ruby applications.
- Check whether Ubuntu Pro is attached, since the fix is delivered through ESM Apps. Ubuntu says Pro is free for up to five machines.
- Install the fixed ruby-openid package version for your release with a standard system update.
- Restart the Ruby application or application server so it loads the updated library.
- Check Gemfile.lock in each Ruby project for a bundled copy of ruby-openid and plan an update or removal if you do not need OpenID.
- Restrict outbound traffic from application servers to only the destinations they need, which limits what any SSRF can reach.
- If you no longer use OpenID login, remove the library from the application.
Ubuntu states that in general a standard system update makes all the necessary changes. With Pro attached, this command refreshes the package lists and upgrades only ruby-openid. Afterwards, run the dpkg check again and confirm the version matches the fixed one for your release.
sudo apt update && sudo apt install --only-upgrade ruby-openidFor systems without Pro, Ubuntu says only that a community fix might become publicly available in the future. There is no date, so do not plan around it; attaching Pro is the route Ubuntu documents today.
Detection and monitoring
As general guidance for SSRF-type bugs, watch for unexpected outbound connections from your web servers, especially right after requests to the OpenID login endpoint. Review egress or firewall logs for connections from application hosts to internal ranges or unfamiliar external hosts. Application logs that record failed OpenID verifications can also help, because the behavior Ubuntu describes happens before verification completes.
For wider hygiene, a WAF can help filter suspicious requests to login endpoints, and the small business website security guide covers patching routines. Certificate and DNS monitoring will not detect this flaw, but it helps you notice other unexpected changes on the same hosts.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
