Skip to main content
VulnerabilityPublished

CVE-2026-129885: unrolled secure · Reliance on Untrusted Inputs in a Security Decision

Affects unrolled secureSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 1.18.0 when convenient.

Data as of 16 Nov 2026, 14:51 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.3
CNA (VulnCheck)CVSS 3.13.7
Patch
Available – fixed in 1.18.0
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade unrolled secure to 1.18.0.

Affected software

ProductAffectedFixed in
unrolledsecureAffected
  • <1.18.0
Fixed in
  • 1.18.0
Gosecurepkg:golang/secureOther threatsAffected
  • <1.18.0
Fixed in
  • 1.18.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade unrolled Secure to version 1.18.0 or later, where this vulnerability is fixed. No other mitigation is indicated as the fix is available and official.

Description

Unrolled Secure versions before 1.18.0 have a vulnerability in the Secure.isSSL() function where the client-supplied URL scheme is trusted to determine if the transport is HTTPS. This allows attackers to bypass HTTPS redirects by sending plaintext HTTP requests with an absolute-form https:// request-target, causing responses to be served unencrypted.

References

Community reviews

Loading reviews…