Summary
Arc has unauthenticated application log disclosure via /api/v1/logs
Impact
An unauthenticated network attacker can retrieve recent application logs. Depending on deployment and log level, logs can disclose operational metadata such as component names, internal paths, database/measurement names, node identifiers, caller locations, request outcomes, and error details. This can assist further attacks and may expose sensitive data if any deployment logs secrets or user-controlled confidential data.
The audit did not confirm that the bootstrap admin token banner is captured by this endpoint; that banner is printed with fmt.Fprintf(os.Stderr, ...), while this endpoint reads the zerolog-backed application buffer.
A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
- Move
/api/v1/logsregistration after global auth middleware and require an authenticated administrator; or - Add explicit route-level middleware:
auth.RequireAdmin(authManager)for/api/v1/logs; and - Add a regression test that unauthenticated requests to
/api/v1/logsreturn 401/403 while/healthand/readyremain public.
Frequently Asked Questions
- What is GHSA-M3QR-FVP4-78XJ? GHSA-M3QR-FVP4-78XJ is a low-severity missing authentication for critical function vulnerability in github.com/basekick-labs/arc (go), affecting versions < 0.0.0-20260615165136-bb7d9761ad98. It is fixed in 0.0.0-20260615165136-bb7d9761ad98. A critical operation is accessible without requiring any authentication.
- Which versions of github.com/basekick-labs/arc are affected by GHSA-M3QR-FVP4-78XJ? github.com/basekick-labs/arc (go) versions < 0.0.0-20260615165136-bb7d9761ad98 is affected.
- Is there a fix for GHSA-M3QR-FVP4-78XJ? Yes. GHSA-M3QR-FVP4-78XJ is fixed in 0.0.0-20260615165136-bb7d9761ad98. Upgrade to this version or later.
- Is GHSA-M3QR-FVP4-78XJ exploitable, and should I be worried? Whether GHSA-M3QR-FVP4-78XJ is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-M3QR-FVP4-78XJ is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-M3QR-FVP4-78XJ? Upgrade
github.com/basekick-labs/arcto 0.0.0-20260615165136-bb7d9761ad98 or later.