On this page (6 sections)
Ubuntu has published USN-9145-1 on 17 November 2026, covering a weakness in OAR, a batch scheduler for HPC (high-performance computing) clusters. The notice says the oarsh script did not properly filter OpenSSH options, and that an authenticated user could possibly use this to obtain sensitive information or escalate privileges.
If you run OAR on Ubuntu 16.04 LTS with Ubuntu Pro (ESM) updates, this is for you. Most websites never run OAR, so this is mainly relevant to research, university and compute environments, and to administrators who host them.
What happened
Ubuntu's notice describes one issue: the oarsh script in OAR did not properly filter OpenSSH options. The notice describes the impact in general terms only, saying OAR could be made to expose sensitive information or run programs with elevated privileges. It references CVE-2016-1235.
The notice does not include a CVSS score, exploitation details, or a statement on whether the flaw is being exploited. Only one publisher, Ubuntu, covers this story so far, so treat any detail beyond the notice as unconfirmed.
What unfiltered options can mean
As general background, not something the notice spells out: when a script accepts options from a user and hands them to another program without filtering, the caller may be able to change behavior the script's author never intended to expose. This weakness class is often called option or argument injection. The notice does not detail how it applies to oarsh, and this article does not speculate on exploitation.
What the notice does say is that the user must be authenticated. That means this is not described as a flaw an anonymous visitor on the internet could use directly. The realistic concern is a legitimate account, or a compromised one, gaining more access than intended.
Who is affected
- Systems running the OAR packages oar-common, oar-node or oar-user on Ubuntu 16.04 LTS (xenial).
- Shared environments where many users hold accounts, since the issue involves an authenticated user.
- Setups where researchers, students or contractors have shell access to machines running OAR.
The notice lists only Ubuntu 16.04 LTS, with fixed versions published as ESM (Expanded Security Maintenance) builds. Ubuntu says Ubuntu Pro provides ten-year security coverage for packages in Main and Universe, and is free for up to five machines. Other releases and other distributions are not covered by this notice, so check your own vendor's advisories if you run OAR elsewhere.
How to check your exposure
The following command lists installed OAR packages and their versions on Ubuntu or Debian-based systems. It is read-only. Look for oar-common, oar-node and oar-user, and check whether the version on 16.04 is older than 2.5.6-2ubuntu1+esm1.
dpkg -l | grep -i oarTo confirm the release you are on, this command prints the Ubuntu version. The affected release in the notice is 16.04 LTS.
lsb_release -aWhat to do now
Ubuntu states that a standard system update makes the necessary changes. The commands below upgrade only the three OAR packages, so run them in a maintenance window if jobs are running.
sudo apt update
sudo apt install --only-upgrade oar-common oar-node oar-userAfterwards, run the dpkg query again and confirm all three packages show 2.5.6-2ubuntu1+esm1.
- Identify every host running oar-common, oar-node or oar-user.
- Confirm which are on Ubuntu 16.04 LTS and whether Ubuntu Pro (ESM) is enabled, since the fix is delivered as an ESM build.
- Update the three packages to 2.5.6-2ubuntu1+esm1 and verify with dpkg.
- Review which users hold accounts on these systems and remove any that are no longer needed.
- Review authentication and system logs as general hygiene, keeping in mind that the notice gives no indicators of exploitation.
- Plan a move to a supported Ubuntu release. The fix for 16.04 comes as an ESM build through Ubuntu Pro, which Ubuntu says is free for up to five machines.
Hardening and monitoring afterwards
The notice gives no exploitation status and no indicators of compromise, so there is no specific signature to search for. Treat the following as general hardening rather than detection of this flaw: keep the list of accounts with shell access short, review authentication logs periodically, and watch for unexpected changes to SSH configuration or authorized keys on machines that run OAR.
If any services on these systems are reachable from the internet, such as a web portal, keep their certificates and DNS under watch. The free SSL checker can verify a certificate, and Webforta Monitor can alert you to certificate and DNS changes. Neither addresses this OAR flaw directly; the fix is the package update.
For broader patching habits, see the small business website security guide and our security news archive.
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.
