[Eclipse CSI - otterdog] OS Command Injection and Arbitrary Code Execution
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 27/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
OS command injection in the pass and bitwarden credential providers of Eclipse Otterdog lets a user who can modify an organization configuration run arbitrary commands with the privileges of the operator running otterdog, including access to their credential vault. The attack is carried out remotely through a crafted secret reference or credential identifier that is resolved when "otterdog apply" runs, and it requires low-privilege login and some user action.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach10/20Affects PyPI packages
- Severity8.8/10CVSS 8.8
- No patch5/5No patch listed yet
What would change the score
- Would score about 82 if added to CISA KEV
- Would score about 77 if CISA's SSVC rates exploitation active
- Would score about 46 if advisories confirm default setups are exposed
Impact
- Widely used
otterdog has 76 weekly downloads.Source: pypistats.org
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-123717 ([Eclipse CSI - otterdog] OS Command Injection and Arbitrary Code Execution), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-123717 (entry last updated 2026-11-10): Affected: - PyPI package otterdog: from 0.1.0, through 1.7.1 Fixed versions: none listed yet. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-123717 is not listed as of cve.now's last read. This KEV status is for CVE-2026-123717 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Packages (PyPI): find every lockfile in each project and run check_stack from the cve.now MCP server on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies. Verify against the linked advisories before concluding, and cite the date you read each one: - https://github.com/eclipse-csi/otterdog/security/advisories/GHSA-886p-g538-rcmp - https://github.com/eclipse-csi/otterdog/releases/tag/v1.8.0 - https://gitlab.eclipse.org/security/cve-assignment/-/work_items/552 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-123717 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-123717.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- otterdogPyPI
From 0.1.0 · through 1.7.1
No fix released. The latest release, 1.7.1, is still affected.
Evidence 5
Vendor advisory · 2
Establishes: Affected and fixed versions.
- Advisory
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123717
Is CVE-2026-123717 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-123717?
otterdog (PyPI): from 0.1.0 through 1.7.1.Source: cve.now feed data