Security readout for executives and security teams
Plain-English summary
browserstack-local 1.5.8 has a command injection flaw tied to unsafe handling of the logfile variable. If an attacker with local low-privilege access can influence that value, they may execute commands with the process privileges. The source bundle does not name a fixed version or vendor mitigation.
Executive priority
Treat as high priority where BrowserStack Local runs in shared developer, CI, or build environments. The business risk is stronger when low-privileged users can influence job configuration or filesystem paths.
Technical view
The CVE describes improper sanitization of logfile in lib/Local.js, mapped to CWE-78 and CWE-94. CVSS 3.1 is 7.8: local attack vector, low complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely in development, CI, QA, or test automation environments that use browserstack-local 1.5.8 and allow untrusted or low-privileged users to control logfile configuration.
Exploitation context
The source bundle does not indicate CISA KEV listing or active exploitation. The stated attack path is local, requires low privileges, and does not require user interaction. Evidence is incomplete on public exploit maturity and real-world targeting.
Researcher notes
The provided CVE data identifies the vulnerable variable and file but does not provide a patch reference, affected CPEs, or complete product metadata. Validate package provenance and fixed-version status directly from npm or maintainer guidance.
Mitigation direction
- Inventory projects and CI images for browserstack-local 1.5.8.
- Check npm and vendor guidance for a fixed or recommended version.
- Avoid passing untrusted input into the logfile option.
- Restrict local access to systems running BrowserStack Local jobs.
- If no fix is available, evaluate temporary removal or isolation.
Validation and detection
- Review package lockfiles and dependency manifests for browserstack-local 1.5.8.
- Inspect CI and test configurations for logfile usage.
- Confirm whether logfile values can be influenced by users or pipeline variables.
- Review endpoint telemetry for unexpected child processes during BrowserStack Local runs.
- Track Red Hat, CVE, npm, and referenced advisory updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-57283 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADPCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-01-28T16:01:31.833Z: Reported to Red Hat.
- 2026-01-28T00:00:00.000Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.npmjs.com/CVE reference, mitre
- https://gist.github.com/Dremig/b639c61541dd1482007dc7a5cd7fefb1CVE reference, mitre
- https://access.redhat.com/security/cve/CVE-2025-57283CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2433928CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-57283.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.