Mercury Agent
Monthly
Server-side request forgery in cosmicstack-labs Mercury Agent (versions 1.1.0 through 1.1.13) lets an attacker who can influence the `path` argument of the GitHub API handler force the agent to issue requests to arbitrary hosts, including internal services reachable from the agent's network position. The flaw is in the githubRequest function of src/utils/github.ts (CWE-918), and publicly available exploit code exists — the reporter's tracking issue (#81) on the project repository is public. The maintainer was informed early through an issue report but has not responded, so no vendor-released fix is confirmed at time of analysis.
Mercury Agent versions through 1.1.13 gate shell execution by validating commands before canonicalizing them, so a caller with low privileges can craft input that passes the raw-string permission check yet resolves to a protected target, disclosing restricted data over the network. The flaw is a validate-before-canonicalize ordering error (CWE-180) in checkShellCommand within src/capabilities/permissions.ts, and publicly available exploit code exists via the project's own issue tracker. The project was notified early but has not responded, so no vendor fix is available, and the CVSS 4.0 base score of 2.1 reflects only a limited confidentiality impact.
A local information-disclosure weakness in cosmicstack-labs mercury-agent through version 1.2.0 lets a low-privileged local user manipulate the Shell Permission Manifest so that PermissionManager.checkShellCommand in mercury-agent/src/capabilities/permissions.ts mis-evaluates which shell commands are permitted. Successful abuse exposes sensitive data readable through the agent's shell capability, though integrity and availability are unaffected. Public exploit code exists (linked issue report) and the vendor has not yet responded, but exploitation is limited to hosts already running the agent and requires local access, giving a very low CVSS 4.0 base score of 1.9.
Improper authorization in cosmicstack-labs mercury-agent's PermissionManager.checkShellCommand function (versions 1.1.0 through 1.1.13) allows authenticated remote attackers to bypass the shell command permission gate enforced in mercury-agent/src/capabilities/permissions.ts. A public exploit was released via GitHub issue #101, and the vendor has not responded to the coordinated disclosure. The CVSS 4.0 base score is 2.1 (low), reflecting constrained impact due to authentication prerequisites and limited C/I/A blast radius, with no CISA KEV listing confirmed at time of analysis.
Improper authorization in cosmicstack-labs mercury-agent's delegate_task tool allows a remotely authenticated low-privilege attacker to invoke SubAgent.run operations beyond their permitted scope in all versions through 1.1.12. No vendor patch has been released - the project was notified via issue report but has not responded. A public proof-of-concept exploit exists (GitHub issue #74), lowering the bar for exploitation in any exposed deployment.
Incorrect authorization in cosmicstack-labs mercury-agent through version 1.1.12 allows remote authenticated attackers to bypass access controls via the bg Command Handler. The flaw (CWE-863) resides in Agent.handleBgCommand within src/core/agent.ts, where a present-but-flawed authorization check can be manipulated to execute unauthorized background commands. A proof-of-concept exploit is publicly available via GitHub issue #73; the vendor has not responded to responsible disclosure and no patch exists at time of analysis.
Incorrect privilege assignment in cosmicstack-labs mercury-agent (all versions through 1.1.12) allows authenticated remote attackers to bypass shell command permission checks via the run_command Handler. The flaw resides in the PermissionManager.checkShellCommand function within src/capabilities/permissions.ts, where privilege levels are not correctly validated, potentially enabling a low-privileged user to execute shell commands exceeding their authorized scope. A public proof-of-concept exploit exists via GitHub issue #72, and the project maintainer has not responded to responsible disclosure, leaving no vendor-released patch available at time of analysis.
Server-side request forgery in cosmicstack-labs Mercury Agent (versions 1.1.0 through 1.1.13) lets an attacker who can influence the `path` argument of the GitHub API handler force the agent to issue requests to arbitrary hosts, including internal services reachable from the agent's network position. The flaw is in the githubRequest function of src/utils/github.ts (CWE-918), and publicly available exploit code exists — the reporter's tracking issue (#81) on the project repository is public. The maintainer was informed early through an issue report but has not responded, so no vendor-released fix is confirmed at time of analysis.
Mercury Agent versions through 1.1.13 gate shell execution by validating commands before canonicalizing them, so a caller with low privileges can craft input that passes the raw-string permission check yet resolves to a protected target, disclosing restricted data over the network. The flaw is a validate-before-canonicalize ordering error (CWE-180) in checkShellCommand within src/capabilities/permissions.ts, and publicly available exploit code exists via the project's own issue tracker. The project was notified early but has not responded, so no vendor fix is available, and the CVSS 4.0 base score of 2.1 reflects only a limited confidentiality impact.
A local information-disclosure weakness in cosmicstack-labs mercury-agent through version 1.2.0 lets a low-privileged local user manipulate the Shell Permission Manifest so that PermissionManager.checkShellCommand in mercury-agent/src/capabilities/permissions.ts mis-evaluates which shell commands are permitted. Successful abuse exposes sensitive data readable through the agent's shell capability, though integrity and availability are unaffected. Public exploit code exists (linked issue report) and the vendor has not yet responded, but exploitation is limited to hosts already running the agent and requires local access, giving a very low CVSS 4.0 base score of 1.9.
Improper authorization in cosmicstack-labs mercury-agent's PermissionManager.checkShellCommand function (versions 1.1.0 through 1.1.13) allows authenticated remote attackers to bypass the shell command permission gate enforced in mercury-agent/src/capabilities/permissions.ts. A public exploit was released via GitHub issue #101, and the vendor has not responded to the coordinated disclosure. The CVSS 4.0 base score is 2.1 (low), reflecting constrained impact due to authentication prerequisites and limited C/I/A blast radius, with no CISA KEV listing confirmed at time of analysis.
Improper authorization in cosmicstack-labs mercury-agent's delegate_task tool allows a remotely authenticated low-privilege attacker to invoke SubAgent.run operations beyond their permitted scope in all versions through 1.1.12. No vendor patch has been released - the project was notified via issue report but has not responded. A public proof-of-concept exploit exists (GitHub issue #74), lowering the bar for exploitation in any exposed deployment.
Incorrect authorization in cosmicstack-labs mercury-agent through version 1.1.12 allows remote authenticated attackers to bypass access controls via the bg Command Handler. The flaw (CWE-863) resides in Agent.handleBgCommand within src/core/agent.ts, where a present-but-flawed authorization check can be manipulated to execute unauthorized background commands. A proof-of-concept exploit is publicly available via GitHub issue #73; the vendor has not responded to responsible disclosure and no patch exists at time of analysis.
Incorrect privilege assignment in cosmicstack-labs mercury-agent (all versions through 1.1.12) allows authenticated remote attackers to bypass shell command permission checks via the run_command Handler. The flaw resides in the PermissionManager.checkShellCommand function within src/capabilities/permissions.ts, where privilege levels are not correctly validated, potentially enabling a low-privileged user to execute shell commands exceeding their authorized scope. A public proof-of-concept exploit exists via GitHub issue #72, and the project maintainer has not responded to responsible disclosure, leaving no vendor-released patch available at time of analysis.