{"answers":{"affected":"3 open source packages ship an affected version, including github.com/alexandre-daubois/ember.","exploited":"There is no known exploitation of CVE-2026-54162 in the wild and no public exploit code.","fix":"Upgrade github.com/alexandre-daubois/ember to 1.4.2 or later.","what":"CVE-2026-54162 is a medium-severity vulnerability in alexandre-daubois ember, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-54162 and fix it if it is affected.\n\nWhat it is: CVE-2026-54162 is a medium-severity vulnerability in alexandre-daubois ember, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-54162 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/alexandre-daubois/ember (Go): affected all versions; fixed in 1.4.2\n- github.com/alexandre-daubois/ember (Go): affected all versions; fixed in 1.4.2\n- github.com/alexandre-daubois/ember (Go): affected all versions; fixed in 1.4.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54162/ (Markdown: https://insights.sbomify.com/CVE-2026-54162/index.md)","id":"CVE-2026-54162","markdown":"https://insights.sbomify.com/CVE-2026-54162/index.md","name":"CVE-2026-54162","record":{"aliases":["GHSA-x3g7-qrwc-f6c5","GO-2026-6270"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":4.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-150","name":"Improper Neutralization of Escape, Meta, or Control Sequences"}],"description":"Ember is a real-time terminal dashboard for Caddy servers with FrankenPHP support. Prior to 1.4.2, interactive TUI row formatters pass Caddy access-log fields, particularly the request URI, through the `fitCellLeft` render helper without neutralizing terminal escape or control sequences. An unauthenticated remote client can place ANSI, OSC, or CSI control bytes in an ordinary HTTP request target. Caddy JSON-escapes those bytes, `ParseLogLine` decodes them back into raw controls, and the formatters concatenate them into `View()` output reaching `os.Stdout`. When the operator views the default `Logs` tab, the terminal interprets these sequences, allowing monitoring-dashboard spoofing, clipboard hijacking through `OSC 52`, and window-title spoofing through `OSC 0/2`. This works even with a loopback-only log listener because the input arrives through normal Caddy access logs. `Certificates` and `Routes` share secondary unneutralized render sinks. The `--json`, `--once`, and daemon `--expose` modes are unaffected because they do not render an interactive terminal. Consequences depend on the terminal emulator and usually require further operator action to escalate; this is not general-purpose remote code execution. This issue is fixed in version 1.4.2.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Ember: Unneutralised terminal escape/control sequences from Caddy logs injected into the operator's TUI","id":"CVE-2026-54162","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":null,"year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"secure_headers: CSP directive injection via sandbox, plugin_types, and report_to when given untrusted input","id":"CVE-2026-54163"},"packages":[{"ecosystem":"Go","fixed":["1.4.2"],"introduced":["0"],"last_affected":[],"package":"github.com/alexandre-daubois/ember","purl":null,"source":"GHSA-x3g7-qrwc-f6c5"},{"ecosystem":"Go","fixed":["1.4.2"],"introduced":["0"],"last_affected":[],"package":"github.com/alexandre-daubois/ember","purl":"pkg:golang/github.com/alexandre-daubois/ember","source":"GHSA-x3g7-qrwc-f6c5"},{"ecosystem":"Go","fixed":["1.4.2"],"introduced":["0"],"last_affected":[],"package":"github.com/alexandre-daubois/ember","purl":"pkg:golang/github.com/alexandre-daubois/ember","source":"GO-2026-6270"}],"prev":{"headline":"Network UPS Tools: A PWN Request in make-dist workflow can execute PR-controlled code with write-scoped GITHUB_TOKEN","id":"CVE-2026-54160"},"products":["ember"],"published":"2026-10-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-29","vendors":["alexandre-daubois"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-54162/"}