dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-0855

HIGH · 8.8 CVSS v3.1 Published 2026-01-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
Certain IP Camera models developed by Merit LILIN has a OS Command Injection vulnerability, allowing authenticated remote attackers to inject arbitrary OS commands and execute them on the device.

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 Merit LILIN IP camera firmware allows authenticated remote attackers to inject and execute arbitrary OS commands through unsanitized input fields in the web interface or API.

MitigationApply vendor-supplied firmware patches when available; if no patch exists, consider network segmentation and strict access controls to limit exposure to authenticated users, and monitor for indicators of compromise.

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
High

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

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 device is a Merit LILIN IP camera
    Access the device web interface or check network inventory to identify the device manufacturer and model. Merit LILIN devices typically have 'LILIN' branding in the web interface or can be identified via MAC address OUI lookup (LILIN OUI prefixes).
    Affected if The device is not a Merit LILIN IP camera, then this specific CVE does not apply.
  2. Retrieve the installed firmware version
    Log into the camera web interface and navigate to System > Information or Firmware/Version settings page. Alternatively, use the camera's API endpoint (often /cgi-bin/api or similar) to query firmware version via HTTP request.
    Affected if Unable to determine firmware version; assume potentially affected if the device is a Merit LILIN IP camera.
  3. Check if the web management interface is network-accessible
    Verify that TCP ports 80, 443, or the camera's web service port are open and reachable from untrusted networks. Use nmap or network scanning to confirm exposure: nmap -p 80,443 <camera-ip>
    Affected if The web interface is directly exposed to the internet or untrusted networks, increasing exposure to authenticated attackers.
  4. Verify authentication is required for the web interface
    Attempt to access the camera web interface without credentials. If the login page is presented and unauthenticated access to command-injection-prone pages is denied, authentication is enforced. Check for any configuration that allows anonymous or default credential access.
    Affected if The web interface permits unauthenticated access or uses default/weak credentials, allowing attackers to gain the authentication required to exploit the command injection.
  5. Inspect input fields in the web interface for sanitization
    If you have access, navigate to configuration areas that accept user input (such as network settings, device naming, or API parameter fields). Observe whether special characters (such as ; | & $ `) are accepted without error or filtering. This is a manual inspection of input handling.
    Affected if Input fields accept and process special shell characters without sanitization, indicating the vulnerability may be present.

The environment is affected if the device is a Merit LILIN IP camera with accessible web interface, regardless of firmware version, since no specific fixed version is provided and the flaw exists in the command injection handling of authenticated sessions.

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

Apply vendor-supplied firmware patches when available; if no patch exists, consider network segmentation and strict access controls to limit exposure to authenticated users, and monitor for indicators of compromise.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0855 — 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-0855 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