Skip to content

CVE-2026-46368

Is CVE-2026-46368 real, exploitable, or a false positive? Here's the community verdict.

Community verdict: No field verdicts yet. Be the first practitioner to weigh in.

signals

public sources

Exploited in wild
Not listed
CISA KEV
Public exploit
Exploit-DB +1
Metasploit/EDB/PoC
Base severity
8.8 High
CVSS
Exploitation prob.
7%
FIRST EPSS
Weakness
CWE-77
CWE

High CVSS base score, but low real-world exploitation probability (EPSS). Likely less urgent than the score implies.

cisa ssvc

CISA Vulnrichment · assessed

Exploitation
Public PoC
in the wild
Automatable
No
at scale
Technical impact
Total
on success

CISA decision, by how critical the affected system is to you:

  • low impact → Track
  • medium impact → Track*
  • high impact → Attend

Track: normal patch cycle · Track*: watch closely · Attend: patch sooner · Act: patch now. About SSVC ↗

public exploits

links to sources — we don’t host code

A working exploit is publicly available from a maintained source. Treat this as higher urgency and verify your exposure.

baseline read

auto · not a community verdict

Low signal — verdict needed

Few public signals point to active risk. Whether a scanner hit here is a true or false positive depends on your version and config — community verdicts decide.

Based on CVSS · FIRST EPSS

Confirm or dispute →

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

luci-app-https-dns-proxy through 2025.12.29-5 — an optional LuCI web UI add-on for the https-dns-proxy package, distributed through the OpenWrt community packages feed and not installed by default — contains a command injection vulnerability in the setInitAction function. An authenticated user holding the luci.https-dns-proxy ACL permission can inject shell metacharacters through the 'name' parameter of a ubus RPC call to luci.https-dns-proxy setInitAction, resulting in arbitrary command execution as root on the underlying device. Core OpenWrt is not affected; only installations that have opted in to the luci-app-https-dns-proxy package are vulnerable.

Published

Embed this verdict
TruePositive verdict for CVE-2026-46368
Markdown
[![TruePositive verdict](https://www.truepositive.app/cve/CVE-2026-46368/badge.svg)](https://www.truepositive.app/cve/CVE-2026-46368)
HTML
<a href="https://www.truepositive.app/cve/CVE-2026-46368"><img src="https://www.truepositive.app/cve/CVE-2026-46368/badge.svg" alt="TruePositive verdict for CVE-2026-46368"></a>

Live badge that updates automatically as the community verdict changes.

timeline

  1. Published by NVD
  2. CISA SSVC assessment · exploitation: poc

Score and exploit changes tracked since .

Community ground truth

Be the first practitioner to weigh in

So far this is only TruePositive's editorial baseline from public sources. Add your real-world verdict below — it becomes the signal the next person triaging this relies on.

🥇 The first 50 practitioners to contribute earn a Founding Contributor badge.

In your experience, is this finding real and exploitable?

awaiting field verdicts
Real, but not a risk here
Not a real issue

Curated baseline: TruePositive's read from public sources is Real & exploitable — a starting point, not a community verdict.

No account needed. Anonymous verdicts post as an unverified signal. Log in to make yours verified and earn reputation.

Field notes & remediation

Verdicts are the quick signal. Notes are the evidence and fixes behind them.

  • 0
    Field note · TruePositive EditorialCurated

    A working public exploit is published for this, so the barrier to attack is low. Patch this on priority and confirm the fix holds.

Add a field note or remediationoptional
Note type

What are you adding?

Markdown supported · minimum 20 characters.

Same weakness: CWE-77.