Home › Vulnerabilities

Eclipse Foundation Eclipse Otterdog Flaw CVE-2026-123717: Update Now

Published November 10, 2026 · Last updated November 10, 2026

CVE Patch

The short version: CVE-2026-123717 is a high-severity security flaw in Eclipse Foundation Eclipse Otterdog. The National Vulnerability Database (NVD) published it on November 10, 2026, and the score it lists is 8.8 out of 10. When FraudMeNot checked on November 10, 2026, CISA had not added CVE-2026-123717 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.

CVE-2026-123717 is a command injection flaw in Eclipse Otterdog, the Eclipse Foundation's open-source tool for managing GitHub organizations as code. Teams describe their organization's settings, repositories and secrets in configuration files, and Otterdog applies those settings to GitHub. Until version 1.8.0, two of Otterdog's credential integrations built shell commands out of text taken from that configuration, so a crafted secret reference could make Otterdog run arbitrary commands on the computer of whoever applied the configuration.

The Otterdog maintainers fixed the bug in release 1.8.0, published on November 10, 2026. The release notes describe the change in one line: the fix makes Otterdog "invoke the pass and bitwarden CLIs without a shell."

How the injection works

Otterdog can pull secret values from two password managers: pass, the standard Unix password store, and Bitwarden, through its bw command-line client. In configuration, a secret can point to one of them with a reference such as pass:<path> or bitwarden:<item>@<field>.

According to the project's security advisory (GHSA-886p-g538-rcmp), both providers "construct shell command strings by interpolating provider data into f-strings executed via subprocess.getstatusoutput(), which invokes /bin/sh -c." Because the reference text went straight into a shell command, characters such as ; or $( ) inside it were interpreted as extra commands rather than as part of a name.

The advisory also shows the same problem with credential settings in a local Otterdog configuration file, where a crafted Bitwarden item ID or pass path triggered the injection when credentials were resolved.

Who could exploit it

The CVE record describes the attacker as "a user able to modify an organization configuration." In many projects that configuration lives in a shared Git repository that accepts pull requests. The advisory calls this "the most relevant cross-trust-boundary scenario": a malicious reference that gets reviewed and merged runs later, when a maintainer applies the configuration.

Two details make this worse. First, Otterdog resolves these references "before the interactive confirmation prompt," so an operator does not get a chance to stop the apply before the command runs. Second, as the advisory points out, the operator's machine "commonly has access to privileged GitHub credentials/tokens and the unlocked secret backend." The CVE record states that injected commands run "with the privileges of the operator running otterdog, including access to their credential vault."

There is an important precondition. The advisory explains that both providers first check that their backend works, using bw unlock --check or pass ls, and stop if it does not. The injection therefore only triggers for operators who actually use pass or Bitwarden with an accessible, unlocked vault.

Affected and fixed versions

The CVE record lists Otterdog 0.1.0 through 1.7.1 as affected, and the advisory adds that "the vulnerable code predates 0.1.0." Version 1.8.0 is the fixed release, distributed through PyPI as the otterdog package and on GitHub.

Severity and who scored it

The Eclipse Foundation, acting as the CVE Numbering Authority, assigned the CVE and scored it CVSS 4.0 8.8 High, vector AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H. In plain terms: a low-privileged attacker with network access, an attack that depends on preconditions such as a usable vault (AT:P), and active involvement by the victim, who must run the apply (UI:A). The impact is rated high both on the operator's system and on systems beyond it, which fits the exposure of GitHub tokens and vault contents. NVD lists the Eclipse score as secondary and had not added its own; there is no CVSS 3.1 score. The weakness is CWE-78, OS command injection.

The CVE record credits Kiki Lee of PwC HK DarkLab as finder. The release notes credit the report to GitHub user kiki156578 and the fix to GitHub users mbarbero and heurtematte. The advisory notes that the report "was prepared with the assistance of AI tools" and that the reporter validated the claims against the source. CISA had not listed the CVE as exploited when FraudMeNot checked, and none of the official sources mention attacks.

Timeline

  • November 10, 2026, 11:06 UTC: Otterdog 1.8.0 is released, naming CVE-2026-123717 and GHSA-886p-g538-rcmp in its security notes.
  • November 10, 2026: the Eclipse Foundation publishes the CVE record, and the GitHub advisory becomes public at 12:19 UTC.

What to do

These steps are for the people who run otterdog apply or otterdog validate for an organization, usually Eclipse project or GitHub organization administrators, and for maintainers who review changes to an Otterdog configuration repository.

  • Upgrade Otterdog to 1.8.0 or later on every machine and CI runner that applies configurations, for example with pip install --upgrade otterdog, then confirm the installed version.
  • Until you upgrade, do not run apply or validate on configuration you have not checked while the pass or Bitwarden provider is set up and usable on that machine. The advisory says the injection "does not trigger if bw/pass is not installed or not usable," but that is a property of the bug, not a supported mitigation, so treat the upgrade as the fix.
  • Review secret references in recent changes. Look through merged and pending pull requests to the configuration repository for pass: or bitwarden: values that contain shell characters such as ;, |, or $(. Check local otterdog.json` credential blocks the same way.
  • Rotate exposed credentials if anything looks wrong. If a suspicious reference was applied, treat the GitHub tokens and vault secrets available on that machine as exposed and rotate them.

What the official record says about CVE-2026-123717

The record was filed by eclipse.org. In its own words: "OS command injection in the pass and bitwarden credential providers in Eclipse Foundation Eclipse Otterdog through 1.7.1 allows a user able to modify an organization configuration to execute arbitrary commands with the privileges of the operator running otterdog, including access to their credential vault, via a crafted secret reference (pass:<path> or bitwarden:<item>@<field>) or credential identifier that is resolved when otterdog apply is run."

Why Eclipse Otterdog admins should care

Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on eclipse.org rated CVE-2026-123717 8.8 (High) under CVSS 4.0. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker needs a low-privilege account; a user has to take a deliberate action. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping Eclipse Otterdog running is high. Scoring string: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X.

Affected Eclipse Otterdog releases

According to the record, these releases are vulnerable:

  • 0.1.0 through 1.7.1

The type of bug behind CVE-2026-123717

NVD classifies it using MITRE's Common Weakness Enumeration:

  • CWE-78, Improper Neutralization of Special Elements used in an OS Command. MITRE describes this class of bug as follows: "The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command before it is sent to a downstream component. (Roles: Attack-Focused, Common-Name, Attack-Focused)"

Vendor remediation for CVE-2026-123717

The vendor advisory remediation for operators of Eclipse Otterdog, quoted for this page, is: "Patch: upgrade otterdog (PyPI/GitHub, eclipse-csi/otterdog) from 0.1.0-1.7.1 to 1.8.0 or later (released 2026-11-10; 'invoke the pass and bitwarden CLIs without a shell'). Until upgraded, do not run otterdog apply/validate on unreviewed configuration while the pass or Bitwarden provider is usable; review pass:/bitwarden: references and otterdog.json credential blocks for shell characters; rotate GitHub tokens and vault secrets if a suspicious reference was applied. Who acts: Otterdog operators (GitHub organization admins, CI runners) and config-repo reviewers. Score: Eclipse Foundation (CNA) CVSS 4.0 8.8 High AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H (NVD Secondary; no CVSS 3.1; no NVD-authored score). Not in CISA KEV as of 2026-11-10 10:21 ET."

What to do about it

  • Update now: Patch: upgrade otterdog (PyPI/GitHub, eclipse-csi/otterdog) from 0.1.0-1.7.1 to 1.8.0 or later (released 2026-11-10; 'invoke the pass and bitwarden CLIs without a shell'). Until upgraded, do not run otterdog apply/validate on unreviewed configuration while the pass or Bitwarden provider is usable; review pass:/bitwarden: references and otterdog.json credential blocks for shell characters; rotate GitHub tokens and vault secrets if a suspicious reference was applied. Who acts: Otterdog operators (GitHub organization admins, CI runners) and config-repo reviewers. Score: Eclipse Foundation (CNA) CVSS 4.0 8.8 High AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H (NVD Secondary; no CVSS 3.1; no NVD-authored score). Not in CISA KEV as of 2026-11-10 10:21 ET.
  • Who should act: IT teams, managed service providers, and developers who run or ship Eclipse Otterdog. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
  • Read the official advisory from Eclipse Foundation (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
  • After patching, confirm the new version is actually running and review logs from November 10, 2026 onward for anything unusual.
  • Home users: you do not need to buy or download anything because of CVE-2026-123717. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.

CVE-2026-123717 record details from CISA and NVD

  • Attack complexity for CVE-2026-123717: low
  • CVE-2026-123717 attack requirements: present
  • Impact on connected systems: secrecy high, integrity high, availability high.
  • Who mapped the weakness type: the address listed on eclipse.org (Primary)
  • References in the NVD record: 3.

Dates to know

  • November 10, 2026: NVD publishes CVE-2026-123717.
  • November 10, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-123717 is not listed.
  • November 10, 2026: most recent NVD update (record status: Received).

Official references

Links listed in the NVD record (labels in brackets come from NVD):

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.