dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-50874

HIGH · 8.1 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An OS command injection vulnerability in the /manage/features/media component of kanishka-linux Reminiscence v0.3.0 allows attackers to execute arbitrary commands via supplying a crafted input.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

OS command injection vulnerability in the /manage/features/media component of kanishka-linux Reminiscence v0.3.0 allows remote attackers to execute arbitrary OS commands by supplying crafted input via the web interface.

MitigationImplement strict input validation and sanitization, avoid using user-supplied data in shell commands, use parameterized APIs or whitelist-based approaches for command execution, and apply principle of least privilege to the application process.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Reminiscence is installed
    Locate the kanishka-linux Reminiscence application in your environment. Check for the web application directory or service process.
    Affected if Reminiscence is not present on the system, the CVE does not apply.
  2. Identify the installed version
    Check the application version by inspecting version files, the application banner, or the web interface footer. Compare against v0.3.0.
    Affected if The installed version is exactly v0.3.0, indicating the affected release.
  3. Verify the /manage/features/media endpoint exists
    Check if the web application exposes the /manage/features/media route. This may require reviewing application routing configuration or attempting to access the endpoint (in a non-production test environment only).
    Affected if The endpoint is accessible, the vulnerable component is present in the deployment.
  4. Inspect web server logs for suspicious requests
    Review access logs for the /manage/features/media path with unusual parameter patterns that may indicate command injection attempts (e.g., shell metacharacters like ; | & $ ).

A user is affected if they are running Reminiscence v0.3.0 with the /manage/features/media web component accessible, regardless of whether exploitation has occurred.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and sanitization, avoid using user-supplied data in shell commands, use parameterized APIs or whitelist-based approaches for command execution, and apply principle of least privilege to the application process.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-50874 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-50874 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data