CVE-2026-39823VulnerabilityPublished 11 Nov 2026

Argo workflows: CVE-2026-27142 fixed a vulnerability

Affects argo-workflowsSource GCVE Database

Compare

Mentioned vulnerabilities

CVE-2026-27142

Authoritative record:CVE-2026-39823· Medium 6.1

Not known to be exploited · CVSS 6.1 Medium : upgrade to 4.1.6-r1 when convenient.

Data as of 11 Nov 2026, 04:49 UTC

CVSS 3.1 base score

6.1Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 4.1.6-r1

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade argo-workflows to 4.1.6-r1.

Affected software

Product	Affected	Fixed in
CleanStartargo-workflows`pkg:apk/cleanstart/argo-workflows`Other threats	Affected <4.1.6-r1	Fixed in 4.1.6-r1

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

AI-suggested

Users should upgrade argo-workflows to version 4.1.6-r1 or later, where the vulnerability has been fixed. Since a patch is available, applying the official fix is the recommended mitigation.

Description

A security vulnerability in argo-workflows prior to version 4.1.6-r1 allowed URLs to be improperly escaped inside a <meta> tag's <content> attribute. This flaw could lead to partial compromise of confidentiality and integrity when exploited. The issue has been fixed in version 4.1.6-r1.

Impact

The vulnerability allows an attacker to cause partial loss of confidentiality and integrity, which may result in information disclosure or manipulation of data related to the affected URLs. There is no indication of availability impact. Exploitation requires user interaction but no privileges, and the attack surface is network-based.

Summary

CVE-2026-39823 affects the argo-workflows package by failing to correctly escape URLs within the <content> attribute of <meta> tags. This vulnerability could be exploited remotely without privileges and requires user interaction, potentially leading to partial confidentiality and integrity impacts. The vulnerability is addressed in argo-workflows version 4.1.6-r1.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2026, 04:49 UTC

Technical details

References

Community reviews

Related threats