CVE-2025-68156
Expr has Denial of Service via Unbounded Recursion in Builtin Functions
Expr is an expression language and expression evaluation for Go. Prior to version 1.17.7, several builtin functions in Expr, including flatten, min, max, mean, and median, perform recursive traversal over user-provided data structures without enforcing a maximum recursion depth. If the evaluation environment contains deeply nested or cyclic data structures, these functions may recurse indefinitely until exceed the Go runtime stack limit. This results in a stack overflow panic, causing the host application to crash. While exploitability depends on whether an attacker can influence or inject cyclic or pathologically deep data into the
evaluation environment, this behavior represents a denial-of-service (DoS) risk and affects overall library robustness. Instead of returning a recoverable evaluation error, the process may terminate unexpectedly. In affected versions, evaluation of expressions that invoke certain builtin functions on untrusted or insufficiently validated data structures can lead to a process-level crash due to stack exhaustion. This issue is most relevant in scenarios where Expr is used to evaluate expressions against externally supplied or dynamically constructed environments; cyclic references (directly or indirectly) can be introduced into arrays, maps, or structs; and there are no application-level safeguards preventing deeply nested input data. In typical use cases with controlled, acyclic data, the issue may not manifest. However, when present, the resulting panic can be used to reliably crash the application, constituting a denial of service. The issue has been fixed in the v1.17.7 versions of Expr. The patch introduces a maximum recursion depth limit for affected builtin functions. When this limit is exceeded, evaluation aborts gracefully and returns a descriptive error instead of panicking. Additionally, the maximum depth can be customized by users via builtin.MaxDepth, allowing applications with legitimate deep structures to raise the limit in a controlled manner. Users are strongly encouraged to upgrade to the patched release, which includes both the recursion guard and comprehensive test coverage to prevent regressions. For users who cannot immediately upgrade, some mitigations are recommended. Ensure that evaluation environments cannot contain cyclic references, validate or sanitize externally supplied data structures before passing them to Expr, and/or wrap expression evaluation with panic recovery to prevent a full process crash (as a last-resort defensive measure). These workarounds reduce risk but do not fully eliminate the issue without the patch.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
7.5
Expr has Denial of Service via Unbounded Recursion in Builtin Functions
Expr is an expression language and expression evaluation for Go. Prior to version 1.17.7, several builtin functions in Expr, including flatten, min, max, mean, and median, perform recursive traversal over user-provided data structures without enforcing a maximum recursion depth. If the evaluation environment contains deeply nested or cyclic data structures, these functions may recurse indefinitely until exceed the Go runtime stack limit. This results in a stack overflow panic, causing the host application to crash. While exploitability depends on whether an attacker can influence or inject cyclic or pathologically deep data into the
evaluation environment, this behavior represents a denial-of-service (DoS) risk and affects overall library robustness. Instead of returning a recoverable evaluation error, the process may terminate unexpectedly. In affected versions, evaluation of expressions that invoke certain builtin functions on untrusted or insufficiently validated data structures can lead to a process-level crash due to stack exhaustion. This issue is most relevant in scenarios where Expr is used to evaluate expressions against externally supplied or dynamically constructed environments; cyclic references (directly or indirectly) can be introduced into arrays, maps, or structs; and there are no application-level safeguards preventing deeply nested input data. In typical use cases with controlled, acyclic data, the issue may not manifest. However, when present, the resulting panic can be used to reliably crash the application, constituting a denial of service. The issue has been fixed in the v1.17.7 versions of Expr. The patch introduces a maximum recursion depth limit for affected builtin functions. When this limit is exceeded, evaluation aborts gracefully and returns a descriptive error instead of panicking. Additionally, the maximum depth can be customized by users via builtin.MaxDepth, allowing applications with legitimate deep structures to raise the limit in a controlled manner. Users are strongly encouraged to upgrade to the patched release, which includes both the recursion guard and comprehensive test coverage to prevent regressions. For users who cannot immediately upgrade, some mitigations are recommended. Ensure that evaluation environments cannot contain cyclic references, validate or sanitize externally supplied data structures before passing them to Expr, and/or wrap expression evaluation with panic recovery to prevent a full process crash (as a last-resort defensive measure). These workarounds reduce risk but do not fully eliminate the issue without the patch.
- Record
CVE-2025-68156- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-770
- Updated
- 2026-11-02
EUVDEUVD-2025-203831
7.5
Expr is an expression language and expression evaluation for Go. Prior to version 1.17.7, several builtin functions in Expr, including flatten, min, max, mean, and median, perform recursive traversal over user-provided data structures without enforcing a maximum recursion depth. If the evaluation environment contains deeply nested or cyclic data structures, these functions may recurse indefinitely until exceed the Go runtime stack limit. This results in a stack overflow panic, causing the host application to crash. While exploitability depends on whether an attacker can influence or inject cyclic or pathologically deep data into the
evaluation environment, this behavior represents a denial-of-service (DoS) risk and affects overall library robustness. Instead of returning a recoverable evaluation error, the process may terminate unexpectedly. In affected versions, evaluation of expressions that invoke certain builtin functions on untrusted or insufficiently validated data structures can lead to a process-level crash due to stack exhaustion. This issue is most relevant in scenarios where Expr is used to evaluate expressions against externally supplied or dynamically constructed environments; cyclic references (directly or indirectly) can be introduced into arrays, maps, or structs; and there are no application-level safeguards preventing deeply nested input data. In typical use cases with controlled, acyclic data, the issue may not manifest. However, when present, the resulting panic can be used to reliably crash the application, constituting a denial of service. The issue has been fixed in the v1.17.7 versions of Expr. The patch introduces a maximum recursion depth limit for affected builtin functions. When this limit is exceeded, evaluation aborts gracefully and returns a descriptive error instead of panicking. Additionally, the maximum depth can be customized by users via builtin.MaxDepth, allowing applications with legitimate deep structures to raise the limit in a controlled manner. Users are strongly encouraged to upgrade to the patched release, which includes both the recursion guard and comprehensive test coverage to prevent regressions. For users who cannot immediately upgrade, some mitigations are recommended. Ensure that evaluation environments cannot contain cyclic references, validate or sanitize externally supplied data structures before passing them to Expr, and/or wrap expression evaluation with panic recovery to prevent a full process crash (as a last-resort defensive measure). These workarounds reduce risk but do not fully eliminate the issue without the patch.
- Record
EUVD-2025-203831- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-cfpf-hrx2-8rv6
7.5
Expr has Denial of Service via Unbounded Recursion in Builtin Functions
Several builtin functions in Expr, including flatten, min, max, mean, and median, perform
recursive traversal over user-provided data structures without enforcing a maximum recursion depth.
If the evaluation environment contains deeply nested or cyclic data structures, these functions may recurse indefinitely until exceed the Go runtime stack limit. This results in a stack overflow panic, causing the host application to crash.
While exploitability depends on whether an attacker can influence or inject cyclic or pathologically deep data into the evaluation environment, this behavior represents a denial-of-service (DoS) risk and affects overall library robustness. Instead of returning a recoverable evaluation error, the process may terminate unexpectedly.
Impact
In affected versions, evaluation of expressions that invoke certain builtin functions on untrusted or insufficiently validated data structures can lead to a process-level crash due to stack exhaustion.
This issue is most relevant in scenarios where:
- Expr is used to evaluate expressions against externally supplied or dynamically constructed environments.
- Cyclic references (directly or indirectly) can be introduced into arrays, maps, or structs.
- There are no application-level safeguards preventing deeply nested input data.
In typical use cases with controlled, acyclic data, the issue may not manifest. However, when present, the resulting panic can be used to reliably crash the application, constituting a denial of service.
Patches
The issue has been fixed in the v1.17.7 versions of Expr.
The patch introduces a maximum recursion depth limit for affected builtin functions. When this limit is exceeded, evaluation aborts gracefully and returns a descriptive error instead of panicking.
Additionally, the maximum depth can be customized by users via builtin.MaxDepth, allowing applications with legitimate
deep structures to raise the limit in a controlled manner.
Users are strongly encouraged to upgrade to the patched release, which includes both the recursion guard and comprehensive test coverage to prevent regressions.
Workarounds
For users who cannot immediately upgrade, the following mitigations are recommended:
- Ensure that evaluation environments cannot contain cyclic references.
- Validate or sanitize externally supplied data structures before passing them to Expr.
- Wrap expression evaluation with panic recovery to prevent a full process crash (as a last-resort defensive measure).
These workarounds reduce risk but do not fully eliminate the issue without the patch.
- Record
GHSA-cfpf-hrx2-8rv6- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-770
- Updated
- 2026-11-02
NVD
7.5
Expr is an expression language and expression evaluation for Go. Prior to version 1.17.7, several builtin functions in Expr, including flatten, min, max, mean, and median, perform recursive traversal over user-provided data structures without enforcing a maximum recursion depth. If the evaluation environment contains deeply nested or cyclic data structures, these functions may recurse indefinitely until exceed the Go runtime stack limit. This results in a stack overflow panic, causing the host application to crash. While exploitability depends on whether an attacker can influence or inject cyclic or pathologically deep data into the
evaluation environment, this behavior represents a denial-of-service (DoS) risk and affects overall library robustness. Instead of returning a recoverable evaluation error, the process may terminate unexpectedly. In affected versions, evaluation of expressions that invoke certain builtin functions on untrusted or insufficiently validated data structures can lead to a process-level crash due to stack exhaustion. This issue is most relevant in scenarios where Expr is used to evaluate expressions against externally supplied or dynamically constructed environments; cyclic references (directly or indirectly) can be introduced into arrays, maps, or structs; and there are no application-level safeguards preventing deeply nested input data. In typical use cases with controlled, acyclic data, the issue may not manifest. However, when present, the resulting panic can be used to reliably crash the application, constituting a denial of service. The issue has been fixed in the v1.17.7 versions of Expr. The patch introduces a maximum recursion depth limit for affected builtin functions. When this limit is exceeded, evaluation aborts gracefully and returns a descriptive error instead of panicking. Additionally, the maximum depth can be customized by users via builtin.MaxDepth, allowing applications with legitimate deep structures to raise the limit in a controlled manner. Users are strongly encouraged to upgrade to the patched release, which includes both the recursion guard and comprehensive test coverage to prevent regressions. For users who cannot immediately upgrade, some mitigations are recommended. Ensure that evaluation environments cannot contain cyclic references, validate or sanitize externally supplied data structures before passing them to Expr, and/or wrap expression evaluation with panic recovery to prevent a full process crash (as a last-resort defensive measure). These workarounds reduce risk but do not fully eliminate the issue without the patch.
- Record
CVE-2025-68156- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-770
- Updated
- 2026-11-02
OSV
7.5
Expr has Denial of Service via Unbounded Recursion in Builtin Functions
Expr is an expression language and expression evaluation for Go. Prior to version 1.17.7, several builtin functions in Expr, including flatten, min, max, mean, and median, perform recursive traversal over user-provided data structures without enforcing a maximum recursion depth. If the evaluation environment contains deeply nested or cyclic data structures, these functions may recurse indefinitely until exceed the Go runtime stack limit. This results in a stack overflow panic, causing the host application to crash. While exploitability depends on whether an attacker can influence or inject cyclic or pathologically deep data into the
evaluation environment, this behavior represents a denial-of-service (DoS) risk and affects overall library robustness. Instead of returning a recoverable evaluation error, the process may terminate unexpectedly. In affected versions, evaluation of expressions that invoke certain builtin functions on untrusted or insufficiently validated data structures can lead to a process-level crash due to stack exhaustion. This issue is most relevant in scenarios where Expr is used to evaluate expressions against externally supplied or dynamically constructed environments; cyclic references (directly or indirectly) can be introduced into arrays, maps, or structs; and there are no application-level safeguards preventing deeply nested input data. In typical use cases with controlled, acyclic data, the issue may not manifest. However, when present, the resulting panic can be used to reliably crash the application, constituting a denial of service. The issue has been fixed in the v1.17.7 versions of Expr. The patch introduces a maximum recursion depth limit for affected builtin functions. When this limit is exceeded, evaluation aborts gracefully and returns a descriptive error instead of panicking. Additionally, the maximum depth can be customized by users via builtin.MaxDepth, allowing applications with legitimate deep structures to raise the limit in a controlled manner. Users are strongly encouraged to upgrade to the patched release, which includes both the recursion guard and comprehensive test coverage to prevent regressions. For users who cannot immediately upgrade, some mitigations are recommended. Ensure that evaluation environments cannot contain cyclic references, validate or sanitize externally supplied data structures before passing them to Expr, and/or wrap expression evaluation with panic recovery to prevent a full process crash (as a last-resort defensive measure). These workarounds reduce risk but do not fully eliminate the issue without the patch.
- Record
CVE-2025-68156- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-770
- Updated
- 2026-11-02
OSVDEBIAN-CVE-2025-68156
7.5
Expr is an expression language and expression evaluation for Go. Prior to version 1.17.7, several builtin functions in Expr, including flatten, min, max, mean, and median, perform recursive traversal over user-provided data structures without enforcing a maximum recursion depth. If the evaluation environment contains deeply nested or cyclic data structures, these functions may recurse indefinitely until exceed the Go runtime stack limit. This results in a stack overflow panic, causing the host application to crash. While exploitability depends on whether an attacker can influence or inject cyclic or pathologically deep data into the evaluation environment, this behavior represents a denial-of-service (DoS) risk and affects overall library robustness. Instead of returning a recoverable evaluation error, the process may terminate unexpectedly. In affected versions, evaluation of expressions that invoke certain builtin functions on untrusted or insufficiently validated data structures can lead to a process-level crash due to stack exhaustion. This issue is most relevant in scenarios where Expr is used to evaluate expressions against externally supplied or dynamically constructed environments; cyclic references (directly or indirectly) can be introduced into arrays, maps, or structs; and there are no application-level safeguards preventing deeply nested input data. In typical use cases with controlled, acyclic data, the issue may not manifest. However, when present, the resulting panic can be used to reliably crash the application, constituting a denial of service. The issue has been fixed in the v1.17.7 versions of Expr. The patch introduces a maximum recursion depth limit for affected builtin functions. When this limit is exceeded, evaluation aborts gracefully and returns a descriptive error instead of panicking. Additionally, the maximum depth can be customized by users via builtin.MaxDepth, allowing applications with legitimate deep structures to raise the limit in a controlled manner. Users are strongly encouraged to upgrade to the patched release, which includes both the recursion guard and comprehensive test coverage to prevent regressions. For users who cannot immediately upgrade, some mitigations are recommended. Ensure that evaluation environments cannot contain cyclic references, validate or sanitize externally supplied data structures before passing them to Expr, and/or wrap expression evaluation with panic recovery to prevent a full process crash (as a last-resort defensive measure). These workarounds reduce risk but do not fully eliminate the issue without the patch.
- Record
DEBIAN-CVE-2025-68156- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
Show 32 moreShow less
OSVGHSA-cfpf-hrx2-8rv6
7.5
Expr has Denial of Service via Unbounded Recursion in Builtin Functions
Several builtin functions in Expr, including flatten, min, max, mean, and median, perform
recursive traversal over user-provided data structures without enforcing a maximum recursion depth.
If the evaluation environment contains deeply nested or cyclic data structures, these functions may recurse indefinitely until exceed the Go runtime stack limit. This results in a stack overflow panic, causing the host application to crash.
While exploitability depends on whether an attacker can influence or inject cyclic or pathologically deep data into the evaluation environment, this behavior represents a denial-of-service (DoS) risk and affects overall library robustness. Instead of returning a recoverable evaluation error, the process may terminate unexpectedly.
Impact
In affected versions, evaluation of expressions that invoke certain builtin functions on untrusted or insufficiently validated data structures can lead to a process-level crash due to stack exhaustion.
This issue is most relevant in scenarios where:
- Expr is used to evaluate expressions against externally supplied or dynamically constructed environments.
- Cyclic references (directly or indirectly) can be introduced into arrays, maps, or structs.
- There are no application-level safeguards preventing deeply nested input data.
In typical use cases with controlled, acyclic data, the issue may not manifest. However, when present, the resulting panic can be used to reliably crash the application, constituting a denial of service.
Patches
The issue has been fixed in the v1.17.7 versions of Expr.
The patch introduces a maximum recursion depth limit for affected builtin functions. When this limit is exceeded, evaluation aborts gracefully and returns a descriptive error instead of panicking.
Additionally, the maximum depth can be customized by users via builtin.MaxDepth, allowing applications with legitimate
deep structures to raise the limit in a controlled manner.
Users are strongly encouraged to upgrade to the patched release, which includes both the recursion guard and comprehensive test coverage to prevent regressions.
Workarounds
For users who cannot immediately upgrade, the following mitigations are recommended:
- Ensure that evaluation environments cannot contain cyclic references.
- Validate or sanitize externally supplied data structures before passing them to Expr.
- Wrap expression evaluation with panic recovery to prevent a full process crash (as a last-resort defensive measure).
These workarounds reduce risk but do not fully eliminate the issue without the patch.
- Record
GHSA-cfpf-hrx2-8rv6- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-770
- Updated
- 2026-11-02
OSVRHSA-2025:23664
7.5
Red Hat Security Advisory: opentelemetry-collector security update
- Record
RHSA-2025:23664- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVRHSA-2025:23729
7.5
Red Hat Security Advisory: opentelemetry-collector security update
- Record
RHSA-2025:23729- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVRHSA-2026:0512
7.5
Red Hat Security Advisory: opentelemetry-collector security update
- Record
RHSA-2026:0512- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVRHSA-2026:0513
7.5
Red Hat Security Advisory: opentelemetry-collector security update
- Record
RHSA-2026:0513- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVRHSA-2026:0514
7.5
Red Hat Security Advisory: opentelemetry-collector security update
- Record
RHSA-2026:0514- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVRLSA-2025:23664
7.5
Important: opentelemetry-collector security update
Collector with the supported components for a Rocky Enterprise Software Foundation build of OpenTelemetry
Security Fix(es):
- github.com/expr-lang/expr: Expr: Denial of Service via uncontrolled recursion in expression evaluation (CVE-2025-68156)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
RLSA-2025:23664- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVRLSA-2025:23729
7.5
Important: opentelemetry-collector security update
Collector with the supported components for a Rocky Enterprise Software Foundation build of OpenTelemetry
Security Fix(es):
- github.com/expr-lang/expr: Expr: Denial of Service via uncontrolled recursion in expression evaluation (CVE-2025-68156)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
RLSA-2025:23729- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVROOT-APP-GOBINARY-CVE-2025-68156
7.5
CVE-2025-68156 in rootio-github.com/expr-lang/expr - Patched by Root
Root has patched CVE-2025-68156 in the rootio-github.com/expr-lang/expr package for Root:Go. Multiple fixed versions available.
- Record
ROOT-APP-GOBINARY-CVE-2025-68156- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVALSA-2025:23664 No score
Important: opentelemetry-collector security update
Collector with the supported components for a AlmaLinux build of OpenTelemetry
Security Fix(es):
- github.com/expr-lang/expr: Expr: Denial of Service via uncontrolled recursion in expression evaluation (CVE-2025-68156)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
ALSA-2025:23664- Updated
- 2026-11-02
OSVALSA-2025:23729 No score
Important: opentelemetry-collector security update
Collector with the supported components for a AlmaLinux build of OpenTelemetry
Security Fix(es):
- github.com/expr-lang/expr: Expr: Denial of Service via uncontrolled recursion in expression evaluation (CVE-2025-68156)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
ALSA-2025:23729- Updated
- 2026-11-02
OSVAZL-72727 No score
CVE-2025-68156 affecting package azl-otel-collector 0.127.0-1
Expr is an expression language and expression evaluation for Go. Prior to version 1.17.7, several builtin functions in Expr, including flatten, min, max, mean, and median, perform recursive traversal over user-provided data structures without enforcing a maximum recursion depth. If the evaluation environment contains deeply nested or cyclic data structures, these functions may recurse indefinitely until exceed the Go runtime stack limit. This results in a stack overflow panic, causing the host application to crash. While exploitability depends on whether an attacker can influence or inject cyclic or pathologically deep data into the
evaluation environment, this behavior represents a denial-of-service (DoS) risk and affects overall library robustness. Instead of returning a recoverable evaluation error, the process may terminate unexpectedly. In affected versions, evaluation of expressions that invoke certain builtin functions on untrusted or insufficiently validated data structures can lead to a process-level crash due to stack exhaustion. This issue is most relevant in scenarios where Expr is used to evaluate expressions against externally supplied or dynamically constructed environments; cyclic references (directly or indirectly) can be introduced into arrays, maps, or structs; and there are no application-level safeguards preventing deeply nested input data. In typical use cases with controlled, acyclic data, the issue may not manifest. However, when present, the resulting panic can be used to reliably crash the application, constituting a denial of service. The issue has been fixed in the v1.17.7 versions of Expr. The patch introduces a maximum recursion depth limit for affected builtin functions. When this limit is exceeded, evaluation aborts gracefully and returns a descriptive error instead of panicking. Additionally, the maximum depth can be customized by users via builtin.MaxDepth, allowing applications with legitimate deep structures to raise the limit in a controlled manner. Users are strongly encouraged to upgrade to the patched release, which includes both the recursion guard and comprehensive test coverage to prevent regressions. For users who cannot immediately upgrade, some mitigations are recommended. Ensure that evaluation environments cannot contain cyclic references, validate or sanitize externally supplied data structures before passing them to Expr, and/or wrap expression evaluation with panic recovery to prevent a full process crash (as a last-resort defensive measure). These workarounds reduce risk but do not fully eliminate the issue without the patch.
- Record
AZL-72727- Updated
- 2026-11-05
OSVAZL-72733 No score
CVE-2025-68156 affecting package coredns for versions less than 1.11.4-12
Expr is an expression language and expression evaluation for Go. Prior to version 1.17.7, several builtin functions in Expr, including flatten, min, max, mean, and median, perform recursive traversal over user-provided data structures without enforcing a maximum recursion depth. If the evaluation environment contains deeply nested or cyclic data structures, these functions may recurse indefinitely until exceed the Go runtime stack limit. This results in a stack overflow panic, causing the host application to crash. While exploitability depends on whether an attacker can influence or inject cyclic or pathologically deep data into the
evaluation environment, this behavior represents a denial-of-service (DoS) risk and affects overall library robustness. Instead of returning a recoverable evaluation error, the process may terminate unexpectedly. In affected versions, evaluation of expressions that invoke certain builtin functions on untrusted or insufficiently validated data structures can lead to a process-level crash due to stack exhaustion. This issue is most relevant in scenarios where Expr is used to evaluate expressions against externally supplied or dynamically constructed environments; cyclic references (directly or indirectly) can be introduced into arrays, maps, or structs; and there are no application-level safeguards preventing deeply nested input data. In typical use cases with controlled, acyclic data, the issue may not manifest. However, when present, the resulting panic can be used to reliably crash the application, constituting a denial of service. The issue has been fixed in the v1.17.7 versions of Expr. The patch introduces a maximum recursion depth limit for affected builtin functions. When this limit is exceeded, evaluation aborts gracefully and returns a descriptive error instead of panicking. Additionally, the maximum depth can be customized by users via builtin.MaxDepth, allowing applications with legitimate deep structures to raise the limit in a controlled manner. Users are strongly encouraged to upgrade to the patched release, which includes both the recursion guard and comprehensive test coverage to prevent regressions. For users who cannot immediately upgrade, some mitigations are recommended. Ensure that evaluation environments cannot contain cyclic references, validate or sanitize externally supplied data structures before passing them to Expr, and/or wrap expression evaluation with panic recovery to prevent a full process crash (as a last-resort defensive measure). These workarounds reduce risk but do not fully eliminate the issue without the patch.
- Record
AZL-72733- Updated
- 2026-11-05
OSVAZL-72736 No score
CVE-2025-68156 affecting package keda for versions less than 2.14.1-9
Expr is an expression language and expression evaluation for Go. Prior to version 1.17.7, several builtin functions in Expr, including flatten, min, max, mean, and median, perform recursive traversal over user-provided data structures without enforcing a maximum recursion depth. If the evaluation environment contains deeply nested or cyclic data structures, these functions may recurse indefinitely until exceed the Go runtime stack limit. This results in a stack overflow panic, causing the host application to crash. While exploitability depends on whether an attacker can influence or inject cyclic or pathologically deep data into the
evaluation environment, this behavior represents a denial-of-service (DoS) risk and affects overall library robustness. Instead of returning a recoverable evaluation error, the process may terminate unexpectedly. In affected versions, evaluation of expressions that invoke certain builtin functions on untrusted or insufficiently validated data structures can lead to a process-level crash due to stack exhaustion. This issue is most relevant in scenarios where Expr is used to evaluate expressions against externally supplied or dynamically constructed environments; cyclic references (directly or indirectly) can be introduced into arrays, maps, or structs; and there are no application-level safeguards preventing deeply nested input data. In typical use cases with controlled, acyclic data, the issue may not manifest. However, when present, the resulting panic can be used to reliably crash the application, constituting a denial of service. The issue has been fixed in the v1.17.7 versions of Expr. The patch introduces a maximum recursion depth limit for affected builtin functions. When this limit is exceeded, evaluation aborts gracefully and returns a descriptive error instead of panicking. Additionally, the maximum depth can be customized by users via builtin.MaxDepth, allowing applications with legitimate deep structures to raise the limit in a controlled manner. Users are strongly encouraged to upgrade to the patched release, which includes both the recursion guard and comprehensive test coverage to prevent regressions. For users who cannot immediately upgrade, some mitigations are recommended. Ensure that evaluation environments cannot contain cyclic references, validate or sanitize externally supplied data structures before passing them to Expr, and/or wrap expression evaluation with panic recovery to prevent a full process crash (as a last-resort defensive measure). These workarounds reduce risk but do not fully eliminate the issue without the patch.
- Record
AZL-72736- Updated
- 2026-11-02
OSVGO-2025-4245 No score
Expr has Denial of Service via Unbounded Recursion in Builtin Functions in github.com/expr-lang/expr
Expr has Denial of Service via Unbounded Recursion in Builtin Functions in github.com/expr-lang/expr
- Record
GO-2025-4245- Updated
- 2026-11-02
OSVopenSUSE-SU-2025:15825-1 No score
coredns-for-k8s1.33-1.12.0-2.1 on GA media
These are all security issues fixed in the coredns-for-k8s1.33-1.12.0-2.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2025:15825-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2025:15826-1 No score
coredns-for-k8s1.34-1.12.1-2.1 on GA media
These are all security issues fixed in the coredns-for-k8s1.34-1.12.1-2.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2025:15826-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2025:15832-1 No score
coredns-for-k8s1.35-1.13.1-2.1 on GA media
These are all security issues fixed in the coredns-for-k8s1.35-1.13.1-2.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2025:15832-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:10021-1 No score
coredns-1.14.0-1.1 on GA media
These are all security issues fixed in the coredns-1.14.0-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:10021-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:10067-1 No score
grafana-11.6.7-2.1 on GA media
These are all security issues fixed in the grafana-11.6.7-2.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:10067-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:10073-1 No score
alloy-1.12.2-2.1 on GA media
These are all security issues fixed in the alloy-1.12.2-2.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:10073-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:20099-1 No score
Security update for coredns
This update for coredns fixes the following issues:
Changes in coredns:
-
fix CVE-2025-68156 bsc#1255345
-
fix CVE-2025-68161 bsc#1256411
-
Update to version 1.14.0:
- core: Fix gosec G115 integer overflow warnings
- core: Add regex length limit
- plugin/azure: Fix slice init length
- plugin/errors: Add optional show_first flag to consolidate directive
- plugin/file: Fix for misleading SOA parser warnings
- plugin/kubernetes: Rate limits to api server
- plugin/metrics: Implement plugin chain tracking
- plugin/sign: Report parser err before missing SOA
- build(deps): bump github.com/expr-lang/expr from 1.17.6 to 1.17.7
-
Update to version 1.13.2:
- core: Add basic support for DoH3
- core: Avoid proxy unnecessary alloc in Yield
- core: Fix usage of sync.Pool to save an alloc
- core: Fix data race with sync.RWMutex for uniq
- core: Prevent QUIC reload panic by lazily initializing the listener
- core: Refactor/use reflect.TypeFor
- plugin/auto: Limit regex length
- plugin/cache: Remove superfluous allocations in item.toMsg
- plugin/cache: Isolate metadata in prefetch goroutine
- plugin/cache: Correct spelling of MaximumDefaultTTL in cache and dnsutil packages
- plugin/dnstap: Better error handling (redial & logging) when Dnstap is busy
- plugin/file: Performance finetuning
- plugin/forward: Disallow NOERROR in failover
- plugin/forward: Added support for per-nameserver TLS SNI
- plugin/forward: Prevent busy loop on connection err
- plugin/forward: Add max connect attempts knob
- plugin/geoip: Add ASN schema support
- plugin/geoip: Add support for subdivisions
- plugin/kubernetes: Fix kubernetes plugin logging
- plugin/multisocket: Cap num sockets to prevent OOM
- plugin/nomad: Support service filtering
- plugin/rewrite: Pre-compile CNAME rewrite regexp
- plugin/secondary: Fix reload causing secondary plugin goroutine to leak
-
Update to version 1.13.1:
- core: Avoid string concatenation in loops
- core: Update golang to 1.25.2 and golang.org/x/net to v0.45.0 on CVE fixes
- plugin/sign: Reject invalid UTF‑8 dbfile token
-
Update to version 1.13.0:
- core: Export timeout values in dnsserver.Server
- core: Fix Corefile infinite loop on unclosed braces
- core: Fix Corefile related import cycle issue
- core: Normalize panics on invalid origins
- core: Rely on dns.Server.ShutdownContext to gracefully stop
- plugin/dnstap: Add bounds for plugin args
- plugin/file: Fix data race in tree Elem.Name
- plugin/forward: No failover to next upstream when receiving SERVFAIL or REFUSED response codes
- plugin/grpc: Enforce DNS message size limits
- plugin/loop: Prevent panic when ListenHosts is empty
- plugin/loop: Avoid panic on invalid server block
- plugin/nomad: Add a Nomad plugin
- plugin/reload: Prevent SIGTERM/reload deadlock
-
fix CVE-2025-58063 bsc#1249389
-
Update to version 1.12.4:
- bump deps
- fix(transfer): goroutine leak on axfr err (#7516)
- plugin/etcd: fix import order for ttl test (#7515)
- fix(grpc): check proxy list length in policies (#7512)
- fix(https): propagate HTTP request context (#7491)
- fix(plugin): guard nil lookups across plugins (#7494)
- lint: add missing prealloc to backend lookup test (#7510)
- fix(grpc): span leak on error attempt (#7487)
- test(plugin): improve backend lookup coverage (#7496)
- lint: enable prealloc (#7493)
- lint: enable durationcheck (#7492)
- Add Sophotech to adopters list (#7495)
- plugin: Use %w to wrap user error (#7489)
- fix(metrics): add timeouts to metrics HTTP server (#7469)
- chore(ci): restrict token permissions (#7470)
- chore(ci): pin workflow dependencies (#7471)
- fix(forward): use netip package for parsing (#7472)
- test(plugin): improve test coverage for pprof (#7473)
- build(deps): bump github.com/go-viper/mapstructure/v2 (#7468)
- plugin/file: fix label offset problem in ClosestEncloser (#7465)
- feat(trace): migrate…
- Record
openSUSE-SU-2026:20099-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:20140-1 No score
Security update for alloy
This update for alloy fixes the following issues:
Update to 1.12.2:
Security fixes:
- CVE-2025-68156: github.com/expr-lang/expr/builtin: Fixed potential DoS via unbounded recursion (bsc#1255333):
- CVE-2025-31133, CVE-2025-52565, CVE-2025-52881: github.com/opencontainers/runc: Fixed container breakouts by bypassing runc's restrictions for writing to arbitrary /proc files (bsc#1255074)
Other fixes:
- Add missing configuration parameter
deployment_name_from_replicaset to k8sattributes processor
(5b90a9d) (@dehaansa)
- database_observability: Fix schema_details collector to fetch
column definitions with case sensitive table names (#4872)
(560dff4) (@jharvey10, @fridgepoet)
- deps: Update jose2go to 1.7.0 (#4858) (dfdd341) (@jharvey10)
- deps: Update npm dependencies [backport] (#5201) (8e06c26)
(@jharvey10)
- Ensure the squid exporter wrapper properly brackets ipv6
addresses [backport] (#5205) (e329cc6) (@dehaansa)
- Preserve meta labels in loki.source.podlogs (#5097) (ab4b21e)
(@kalleep)
- Prevent panic in import.git when update fails [backport]
(#5204) (c82fbae) (@dehaansa, @jharvey10)
- show correct fallback alloy version instead of v1.13.0
(#5110) (b72be99) (@dehaansa, @jharvey10)
- Record
openSUSE-SU-2026:20140-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:20654-1 No score
Security update for grafana
This update for grafana fixes the following issues:
Changes in grafana:
-
Update to version 11.6.11: Features and enhancements:
- Alerting: Add limits for the size of expanded notification templates
- Correlations: Remove support for org_id=0 Security:
- CVE-2026-21722: Public dashboards annotations: use dashboard timerange if time selection disabled (bsc#1258136)
-
Update to version 11.6.10: Features and enhancements:
- API: Add missing scope check on dashboards
- Avatar: Require sign-in, remove queue, respect timeout Bug fixes:
- Alerting: Fix a race condition panic in ResetStateByRuleUID
-
Update to version 11.6.9: Features and enhancements:
- Plugins: Add PluginContext to plugins when scenes is disabled Bug fixes:
- Alerting: Fix contacts point issues
-
Update to version 11.6.8: Bug fixes:
- Alerting: Fix unmarshalling of GettableStatus to include time intervals
-
Update to version 11.6.7: Bug fixes:
- Auth: Fix render user OAuth passthrough
- LDAP Authentication: Fix URL to propagate username context as parameter
- Plugins: Dependencies do not inherit parent URL for preinstall
- URLParams: Stringify true values as key=true always (fixes issues with variables with true value)
-
Update to version 11.6.6: Bug fixes:
- Alerting: Fix copying of recording rule fields
- Fix redirection after login when Grafana is served from subpath
-
Update to version 11.6.5: Features and enhancements:
- Alerting: Bump alerting package to include change to NewTLSClient
-
Update to version 11.6.4: Features and enhancements:
- StateTimeline: Add endTime to tooltip
- Unified storage: Respect GF_DATABASE_URL override Bug fixes:
- Alerting: Fix group interval override when adding new rules
- Azure: Fix legend formatting
- Azure: Fix resource name determination in template variable queries
- Graphite: Fix annotation queries
- Graphite: Fix date mutation
- Graphite: Fix nested variable interpolation for repeated rows
-
Update to version 11.6.3: Security:
- Fixes CVE-2025-3415
-
Update to version 11.6.2: Bug fixes:
- Dashboard: Fixes issue with row repeats and first row
- Graphite: Ensure template variables are interpolated correctly
- Graphite: Fix Graphite series interpolation
- Prometheus: Fix semver import path
-
Update to version 11.6.1: Features and enhancements:
- DashboardScenePage: Correct slug in self referencing data links
- GrafanaUI: Use safePolygon close handler for interactive tooltips instead of a delay
- Prometheus: Add support for cloud partners Prometheus data sources Bug fixes:
- Alertmanager: Add Role-Based Access Control via reqAction Field
- GrafanaUI: Remove blurred background from overlay backdrops to improve performance
- InfluxDB: Fix nested variable interpolation
- LDAP test: Fix page crash
- Org redirection: Fix linking between orgs
-
Upgrade to version 11.6.0: Features and enhancements:
- Visualisations: One click links and actions
- Annotations: Add cron syntax support
- WebGL-powered geomaps for better performance
- Alerting: Add alert rule version history Security:
- API keys: Migrate API keys to service accounts at startup
-
CVE-2026-21721: Fix access control by the dashboard permissions API (bsc#1257337)
-
CVE-2026-21720: Fix unauthenticated DoS (bsc#1257349)
-
CVE-2025-68156: Fix potential DoS via unbounded recursion in builtin functions (bsc#1255340)
-
CVE-2025-64751: Drop experimental implementation of authorization Zanzana server/client (bsc#1254113)
-
Use forked wire from Grafana repository instead of external package (jsc#PED-14178).
-
Update to version 11.5.10: Security:
- CVE-2025-47911: Fix parsing HTML documents (bsc#1251454)
- CVE-2025-58190: Fix excessive memory consumption (bsc#1251657) Features and enhancements:
- Update to Go 1.25
- Update to golang.org/x/net v0.45.0 Bug fixes:
- Auth: Fix render user OAuth…
- Record
openSUSE-SU-2026:20654-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21483-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
- Update to version 0.0.20260723T184607 2026-07-23T18:46:07Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-4730 CVE-2026-33022 GHSA-cv4x-93xx-wgfj
- GO-2026-4761 CVE-2026-33211 GHSA-j5q5-j9gm-2w5c
- GO-2026-5102 CVE-2026-45021 GHSA-3vcp-chfh-f6r2
- GO-2026-5272 CVE-2026-40938 GHSA-94jr-7pqp-xhcq
- GO-2026-5486 CVE-2026-40924 GHSA-m2cx-gpqf-qf74
- GO-2026-5542 CVE-2026-40090 GHSA-pj97-4p9w-gx3q
- GO-2026-5630 CVE-2026-25542 GHSA-rmx9-2pp3-xhcr
- GO-2026-5643 CVE-2026-40923 GHSA-rx35-6rhx-7858
- GO-2026-5675 CVE-2026-41492 GHSA-vvf7-6rmr-m29q
- GO-2026-5711 CVE-2026-40161 GHSA-wjxp-xrpv-xpff
- GO-2026-5746 CVE-2026-41567 GHSA-x86f-5xw2-fm2r
- GO-2026-5749 CVE-2026-41328 GHSA-x92x-px7w-4gx4
- GO-2026-5837 CVE-2026-44840 GHSA-q2m9-6jp9-c6mc
- GO-2026-5929 CVE-2026-44342 GHSA-26v7-h57m-gh9m
- GO-2026-5930 CVE-2026-33655 GHSA-6qcr-qxgr-m7fv
- GO-2026-5933 GHSA-3g4q-2f67-2gvh
- GO-2026-5934 GHSA-59qp-cfj3-rp64
- GO-2026-5935 GHSA-7856-g3gv-9wq8
- GO-2026-5936 CVE-2026-53552 GHSA-26rh-24rg-j3vv
- GO-2026-5937 CVE-2026-53508 GHSA-2jcc-mxv7-p3f9
- GO-2026-5938 CVE-2026-53553 GHSA-4g5x-hcwm-82jw
- GO-2026-5939 CVE-2026-10517 GHSA-698x-9w2p-7vvp
- GO-2026-5940 CVE-2026-53572 GHSA-6w3m-4hhp-775q
- GO-2026-5941 CVE-2026-53487 GHSA-gvhc-wv3v-7pf8
- GO-2026-5942 CVE-2026-46600
- GO-2026-5944 CVE-2026-50197 GHSA-659f-rgp5-w4wf
- GO-2026-5945 CVE-2026-6815 GHSA-rmxx-v9rj-vpvg
- GO-2026-5946 CVE-2026-52831 GHSA-v5px-423j-pf7p
- GO-2026-5947 CVE-2026-53649 GHSA-xqhv-chqm-fhcc
- GO-2026-5948 CVE-2026-50554 GHSA-588f-fvcv-xhvf
- GO-2026-5949 CVE-2026-50553 GHSA-rqrh-8wpv-x7hh
- GO-2026-5950 CVE-2026-53602 GHSA-339v-266x-79xr
- GO-2026-5951 CVE-2026-10219 GHSA-6jm8-4fhr-5w64
- GO-2026-5952 CVE-2026-49834 GHSA-9vcr-p3rj-q5q6
- GO-2026-5953 CVE-2026-9094 GHSA-c9w5-qp6m-m395
- GO-2026-5956 CVE-2026-55252 GHSA-h5g6-xmh4-hc37
- GO-2026-5957 CVE-2026-54158 GHSA-5xfx-xj4h-5p7r
- GO-2026-5958 CVE-2026-54068 GHSA-gcm7-57gf-953c
- GO-2026-5959 CVE-2026-54072 GHSA-h29v-hj44-q8cv
- GO-2026-5961 CVE-2026-54069 GHSA-hvr9-72v2-fff3
- GO-2026-5962 CVE-2026-54088 GHSA-m93h-4hw7-5qcm
- GO-2026-5963 CVE-2026-54067 GHSA-mvjr-vv3c-w4qv
- GO-2026-5964 CVE-2026-54066 GHSA-p4m3-mgmm-c664
- GO-2026-5965 CVE-2026-54070 GHSA-w7cg-whh7-xp28
- GO-2026-5966 CVE-2026-54089 GHSA-xqp3-jq6g-x3qm
- GO-2026-5967 CVE-2026-50551 GHSA-56mp-4f3v-fgj2
- GO-2026-5968 CVE-2026-54174 GHSA-fpg8-7664-jc5q
- GO-2026-5969 GHSA-g936-7jqj-mwv8
- GO-2026-5970 CVE-2026-56852
- GO-2026-5973 CVE-2026-54250 GHSA-jxr7-mqhw-9p98
- GO-2026-5974 CVE-2026-44300 GHSA-wmj8-9953-vff5
- GO-2026-5975 CVE-2026-50018 GHSA-42j2-w334-qxw7
- GO-2026-5976 CVE-2026-50141 GHSA-g7mm-9vx7-jm7h
- GO-2026-5977 CVE-2026-50013 GHSA-qrh4-p6v4-mrfg
- GO-2026-5978 CVE-2026-50125 GHSA-qw5r-ppcg-f8rj
- GO-2026-5979 CVE-2026-50006 GHSA-xrcf-6jh3-ggvx
- GO-2026-5980 CVE-2026-50158 GHSA-2c7f-fxww-6w6c
- GO-2026-5981 GHSA-mqxv-9rm6-w8qc
- GO-2026-5982 GHSA-pqg7-v6wh-3pfp
- GO-2026-5984 CVE-2026-53604 GHSA-2p2f-px33-4vv5
- GO-2026-5985 GHSA-7rx3-5wx3-5v76
- GO-2026-5986 CVE-2026-61699 GHSA-cm26-5974-52h8
- GO-2026-5987 CVE-2026-55513 GHSA-g4x6-jcvr-9m3g
- GO-2026-5988 CVE-2026-54628 GHSA-hwrq-8wxh-q4xv
- GO-2026-5989 CVE-2026-55512 GHSA-m3cx-mwpg-32jg
- GO-2026-5990 CVE-2026-54629 GHSA-mf78-3rpf-r784
- GO-2026-5991 CVE-2026-53603 GHSA-q4vm-pq3q-8wgq
- GO-2026-5992 CVE-2026-61549 GHSA-qf34-295c-26v8
- GO-2026-5996 CVE-2026-54450 GHSA-pph6-vfjv-vpjw
- GO-2026-5997 CVE-2026-54452 GHSA-xgch-x3mx-cm3c
- GO-2026-5998 CVE-2026-54495 GHSA-398h-7f66-3h4p
- GO-2026-5999 CVE-2026-10814 GHSA-jh6h-v6mp-h22v
- GO-2026-6002 CVE-2026-58196 GHSA-pr64-jmmf-jp54
- GO-2026-6003 CVE-2026-53714 GHSA-22xc-xg2r-9j7v
- GO-2026-6004 CVE-2026-52833 GHSA-3v79-m2cg-89ww
- GO-2026-6005 CVE-2026-53715 GHSA-8fv2-88gg-hm7q
- GO-2026-6006 CVE-2026-53716 GHSA-cxpq-8v7q-cg56 *…
- Record
openSUSE-SU-2026:21483-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:0037-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
-
Update to version 0.0.20251230T014957 2025-12-30T01:49:57Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2025-4249 CVE-2025-68120 CVE-2025-68120
- GO-2025-4254 CVE-2025-62190 GHSA-gmx5-frv9-9m9f
- GO-2025-4255 CVE-2025-12689 GHSA-j5vq-62gr-8v3r
- GO-2025-4256 CVE-2025-13324 GHSA-x3r8-2hmh-89f5
- GO-2025-4257 CVE-2025-68476 GHSA-c4p6-qg4m-9jmr
- GO-2025-4258 CVE-2025-68938 GHSA-cm54-pfmc-xrwx
- GO-2025-4261 CVE-2025-68939 GHSA-263q-5cv3-xq9g
- GO-2025-4262 CVE-2025-68945 GHSA-7xq4-mwcp-q8fx
- GO-2025-4263 CVE-2025-68942 GHSA-898p-hh3p-hf9r
- GO-2025-4264 CVE-2025-68944 GHSA-f85h-c7m6-cfpm
- GO-2025-4265 CVE-2025-68946 GHSA-hq57-c72x-4774
- GO-2025-4266 CVE-2025-68943 GHSA-jhx5-4vr4-f327
- GO-2025-4267 CVE-2025-68940 GHSA-rrcw-5rjv-vj26
- GO-2025-4268 CVE-2025-68941 GHSA-xfq3-qj7j-4565
-
Update to version 0.0.20251222T181535 2025-12-22T18:15:35Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2025-4241 CVE-2025-11393 GHSA-cc8c-28gj-px38
- GO-2025-4242 CVE-2025-13888 GHSA-pcqx-8qww-7f4v
- GO-2025-4243 GHSA-wh6m-h6f4-rjf4
- GO-2025-4244 CVE-2025-68274 GHSA-c623-f998-8hhv
- GO-2025-4245 CVE-2025-68156 GHSA-cfpf-hrx2-8rv6
- GO-2025-4247 CVE-2025-13352 GHSA-jf5h-xfw4-p8gp
- GO-2025-4250 CVE-2025-14764 GHSA-3g75-q268-r9r6
-
Update to version 0.0.20251216T193914 2025-12-16T19:39:14Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2025-4239 CVE-2025-68113 GHSA-6gvq-jcmp-8959
- GO-2025-4240 CVE-2025-13281 GHSA-r6j8-c6r2-37rr
-
Update to version 0.0.20251216T162327 2025-12-16T16:23:27Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2024-3036 CVE-2024-41265 GHSA-vw7g-3cc7-7rmh
- GO-2024-3057 CVE-2024-41260 GHSA-9v35-4xcr-w9ph
- GO-2025-3437 GHSA-274v-mgcv-cm8j
- GO-2025-3465 CVE-2025-0426 GHSA-jgfp-53c3-624w
- GO-2025-3764 CVE-2024-44905 GHSA-6xp3-p59p-q4fj
- GO-2025-3829 CVE-2025-54410 GHSA-4vq8-7jfc-9cvp
- GO-2025-4116 CVE-2025-47913
- GO-2025-4122 CVE-2025-11777 GHSA-mqcj-8c2g-h97q
- GO-2025-4178 CVE-2025-13870 GHSA-58w6-w55x-6wq8
-
Update to version 0.0.20251215T203741 2025-12-15T20:37:41Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2025-4136 CVE-2025-64708 GHSA-ch7q-53v8-73pc
- GO-2025-4137 CVE-2025-64521 GHSA-xr73-jq5p-ch8r
- GO-2025-4148 CVE-2017-18874 GHSA-8qg8-c7mw-6fj7
- GO-2025-4154 CVE-2025-62155 GHSA-9f46-w24h-69w4
- GO-2025-4161 CVE-2025-65942 GHSA-66jq-2c23-2xh5
- GO-2025-4162 CVE-2025-60633 GHSA-3j9f-7w24-pcqg
- GO-2025-4167 CVE-2025-64715 GHSA-38pp-6gcp-rqvm
- GO-2025-4168 CVE-2025-12419 GHSA-3x39-62h4-f8j6
- GO-2025-4169 CVE-2025-12559 GHSA-4g87-9x45-cx2h
- GO-2025-4170 CVE-2025-12421 GHSA-mp6x-97xj-9x62
- GO-2025-4173 CVE-2025-10543 GHSA-32fw-gq77-f2f2
- GO-2025-4188 CVE-2025-65637 GHSA-4f99-4q7p-p3gh
- GO-2025-4191 CVE-2017-18878 GHSA-h564-6gc2-fcc6
- GO-2025-4199 CVE-2017-18887 GHSA-35c4-5qfp-wxj6
- GO-2025-4200 CVE-2017-18885 GHSA-g78f-6xq7-rrhq
- GO-2025-4201 CVE-2017-18889 GHSA-jp57-4x34-5v94
- GO-2025-4202 CVE-2017-18890 GHSA-m497-hq5x-6jcv
- GO-2025-4203 CVE-2017-18888 GHSA-v2vm-hq26-5jv6
- GO-2025-4204 CVE-2017-18886 GHSA-wvjg-33p9-938h
- GO-2025-4205 CVE-2025-66491 GHSA-7vww-mvcr-x6vj
- GO-2025-4206 CVE-2025-66490 GHSA-gm3x-23wp-hc2c
- GO-2025-4207 CVE-2025-66508 GHSA-7cqv-qcq2-r765
- GO-2025-4208 CVE-2025-66565 GHSA-m98w-cqp3-qcqr
- GO-2025-4209 CVE-2025-66507 GHSA-qmg5-v42x-qqhq
- GO-2025-4210 CVE-2025-67494 GHSA-7wfc-4796-gmg5
- GO-2025-4211 GHSA-m6wq-66p2-c8pc
- GO-2025-4212 GHSA-pfrf-9r5f-73f5
- GO-2025-4213 CVE-2025-67495 GHSA-v959-qxv6-6f8p
- GO-2025-4214 GHSA-4rmq-mc2c-r495
- GO-2025-4215 CVE-2025-65796 GHSA-8jcj-g9f4-qx42
- GO-2025-4216 CVE-2025-65798 GHSA-8p44-g572-557h
- GO-2025-4217 CVE-2025-65795…
- Record
SUSE-SU-2026:0037-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:0327-1 No score
Security update for alloy
This update for alloy fixes the following issues:
Update to 1.12.2:
Security fixes:
- CVE-2025-68156: github.com/expr-lang/expr/builtin: Fixed potential DoS via unbounded recursion (bsc#1255333):
- CVE-2025-31133, CVE-2025-52565, CVE-2025-52881: github.com/opencontainers/runc: Fixed container breakouts by bypassing runc's restrictions for writing to arbitrary /proc files (bsc#1255074)
Other fixes:
- Add missing configuration parameter
deployment_name_from_replicaset to k8sattributes processor
(5b90a9d) (@dehaansa)
- database_observability: Fix schema_details collector to fetch
column definitions with case sensitive table names (#4872)
(560dff4) (@jharvey10, @fridgepoet)
- deps: Update jose2go to 1.7.0 (#4858) (dfdd341) (@jharvey10)
- deps: Update npm dependencies [backport] (#5201) (8e06c26)
(@jharvey10)
- Ensure the squid exporter wrapper properly brackets ipv6
addresses [backport] (#5205) (e329cc6) (@dehaansa)
- Preserve meta labels in loki.source.podlogs (#5097) (ab4b21e)
(@kalleep)
- Prevent panic in import.git when update fails [backport]
(#5204) (c82fbae) (@dehaansa, @jharvey10)
- show correct fallback alloy version instead of v1.13.0
(#5110) (b72be99) (@dehaansa, @jharvey10)
- Record
SUSE-SU-2026:0327-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:0628-1 No score
Security update 5.1.2 for Multi-Linux Manager Client Tools
This update fixes the following issues:
golang-github-QubitProducts-exporter_exporter:
- Non-customer-facing optimization around source building
golang-github-boynux-squid_exporter:
- Update to version 1.13.0 (jsc#PED-14971)
- Add support for squid-internal-mgr path for metrics.
- Update to version 1.12.0
- Add TLS and basic authentication support for the web interface.
- Update to version 1.11.0
- Allow adding custom labels to all metrics.
- Update to version 1.10.0
- Add ability to configure the exporter using environment variables.
- Add support for Squid 6
- Add
squid_upmetric - Add
squid_scrape_duration_secondsmetric - Add
squid_scrape_errormetric
- Update to version 1.9.0
- Add
process_open_fdsmetric to monitor open file descriptors. - Use
CAP_DAC_READ_SEARCHcapability to allow reading process information without running as root.
- Add
- Update to version 1.8.0
- Add various service time metrics to provide more detailed performance data.
- Update to version 1.7.0
- Add support for basic authentication against the Squid proxy.
- Fix
squid_client_http_requests_totalmetric
- Upstream changes for v1.9.0:
- Use
CAP_DAC_READ_SEARCHcapability to allow reading process information without running as root.
- Use
- Upstream changes for v1.8.0:
- Add various service time metrics to provide more detailed performance data.
- Upstream changes for v1.7.0:
Squid proxy.Update to version 1.10.0
- Add ability to configure the exporter using environment variables.
- Add
process_open_fdsmetric to monitor open file descriptors. - Use
CAP_DAC_READ_SEARCHcapability to allow reading process information without running as root. - Add various service time metrics to provide more detailed performance data.
- Add support for basic authentication against the Squid proxy.
- Use current distro go default version. Use auto-versioning on SUSE as well.
golang-github-lusitaniae-apache_exporter:
- Build without apparmor for openSUSE Leap 16, SLES 16 or newer
- Update to version 1.0.10
- Update github.com/prometheus/client_golang to 1.21.1
- Update github.com/prometheus/common to 0.63.0
- Update github.com/prometheus/exporter-toolkit to 0.14.0
- Update to version 1.0.9
- Update github.com/prometheus/client_golang to 1.20.4
- Update github.com/prometheus/common to 0.59.1
- Update github.com/prometheus/exporter-toolkit to 0.13.0
- Migrate logging to log/slog
- Fix signal handler logging
golang-github-prometheus-alertmanager:
- Require gcc11-c++ for building with SLE 12
golang-github-prometheus-node_exporter:
- Require gcc11-c++ for building with SLE 12
golang-github-prometheus-prometheus:
-
Security issues fixed:
- CVE-2025-12816: Interpretation conflict vulnerability allowing bypassing cryptographic verifications (bsc#1255588)
-
Update to 3.5.0 (jsc#PED-13824): This is a Long-Term Support (LTS) release.
- [FEATURE] Remote-write: Add support for Azure Workload Identity as an authentication method for the receiver.
- [FEATURE] PromQL: Add first_over_time(...) and ts_of_first_over_time(...) behind feature flag.
- [FEATURE] Federation: Add support for native histograms with custom buckets (NHCB).
- [ENHANCEMENT] PromQL: Add warn-level annotations for counter reset conflicts in certain histogram operations.
- [ENHANCEMENT] UI: Add scrape interval and scrape timeout to targets page.
-
Update to 3.4.0:
- [FEATURE] SD: Add unified AWS service discovery for ec2, lightsail and ecs services.
- [FEATURE] Native histograms are now a stable, but optional feature.
- [FEATURE] UI: Show detailed relabeling steps for each discovered target.
- [ENHANCEMENT] Alerting: Add 'unknown' state for alerting rules that haven't been evaluated yet.
- [BUGFIX] Scrape: Fix a bug where scrape cache would not be cleared on startup.
-
Update to 3.3.0:
- [FEATURE] Spring Boot 3.3 includes support for the Prometheus Client 1.x.
- [ENHANCEMENT] Dependency…
- Record
SUSE-SU-2026:0628-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:0630-1 No score
Security update 5.1.2 for Multi-Linux Manager Client Tools
This update fixes the following issues:
dracut-saltboot:
- Update to version 1.1.0
- Retry DHCP requests up to 3 times (bsc#1253004)
golang-github-QubitProducts-exporter_exporter:
- Non-customer-facing optimization around source building
golang-github-boynux-squid_exporter:
- Update to version 1.13.0 (jsc#PED-14971)
- Add support for squid-internal-mgr path for metrics.
- Update to version 1.12.0
- Add TLS and basic authentication support for the web interface.
- Update to version 1.11.0
- Allow adding custom labels to all metrics.
- Update to version 1.10.0
- Add ability to configure the exporter using environment variables.
- Add support for Squid 6
- Add
squid_upmetric - Add
squid_scrape_duration_secondsmetric - Add
squid_scrape_errormetric
- Update to version 1.9.0
- Add
process_open_fdsmetric to monitor open file descriptors. - Use
CAP_DAC_READ_SEARCHcapability to allow reading process information without running as root.
- Add
- Update to version 1.8.0
- Add various service time metrics to provide more detailed performance data.
- Update to version 1.7.0
- Add support for basic authentication against the Squid proxy.
- Fix
squid_client_http_requests_totalmetric
- Upstream changes for v1.9.0:
- Use
CAP_DAC_READ_SEARCHcapability to allow reading process information without running as root.
- Use
- Upstream changes for v1.8.0:
- Add various service time metrics to provide more detailed performance data.
- Upstream changes for v1.7.0:
Squid proxy.Update to version 1.10.0
- Add ability to configure the exporter using environment variables.
- Add
process_open_fdsmetric to monitor open file descriptors. - Use
CAP_DAC_READ_SEARCHcapability to allow reading process information without running as root. - Add various service time metrics to provide more detailed performance data.
- Add support for basic authentication against the Squid proxy.
- Use current distro go default version. Use auto-versioning on SUSE as well.
golang-github-lusitaniae-apache_exporter:
- Build without apparmor for openSUSE Leap 16, SLES 16 or newer
- Require Go 1.23 for building
- Update to version 1.0.10
- Update github.com/prometheus/client_golang to 1.21.1
- Update github.com/prometheus/common to 0.63.0
- Update github.com/prometheus/exporter-toolkit to 0.14.0
- Update to version 1.0.9
- Update github.com/prometheus/client_golang to 1.20.4
- Update github.com/prometheus/common to 0.59.1
- Update github.com/prometheus/exporter-toolkit to 0.13.0
- Migrate logging to log/slog
- Fix signal handler logging
golang-github-prometheus-alertmanager:
- Non-customer-facing optimization around source building
golang-github-prometheus-node_exporter:
- Non-customer-facing optimization around source building
golang-github-prometheus-prometheus:
- CVE-2025-12816: Interpretation conflict vulnerability allowing bypassing cryptographic verifications (bsc#1255588)
- Update to 3.5.0 (jsc#PED-13824):
This is a Long-Term Support (LTS) release.
- [FEATURE] Remote-write: Add support for Azure Workload Identity as an authentication method for the receiver.
- [FEATURE] PromQL: Add first_over_time(...) and ts_of_first_over_time(...) behind feature flag.
- [FEATURE] Federation: Add support for native histograms with custom buckets (NHCB).
- [ENHANCEMENT] PromQL: Add warn-level annotations for counter reset conflicts in certain histogram operations.
- [ENHANCEMENT] UI: Add scrape interval and scrape timeout to targets page.
- Update to 3.4.0:
- [FEATURE] SD: Add unified AWS service discovery for ec2, lightsail and ecs services.
- [FEATURE] Native histograms are now a stable, but optional feature.
- [FEATURE] UI: Show detailed relabeling steps for each discovered target.
- [ENHANCEMENT] Alerting: Add 'unknown' state for alerting rules that haven't been evaluated yet.
- [BUGFIX] Scrape: Fix a bug where scrape cache would not be cleared on startup. -…
- Record
SUSE-SU-2026:0630-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:1013-1 No score
Security update 5.0.7 for Multi-Linux Manager Client Tools
This update fixes the following issues:
dracut-saltboot:
-
Version update to 1.1.0:
- Retry DHCP requests up to 3 times (bsc#1253004)
golang-github-QubitProducts-exporter_exporter:
- Non-customer-facing optimization and update
golang-github-boynux-squid_exporter:
-
Version update from 1.6.0 to 1.13.0 with the following highlighted changes and fixes (jsc#PED-14971):
- Added compatibility for Squid 6 and support for the squid-internal-mgr metrics path
- Added TLS and Basic Authentication to the exporter’s web interface
- Added support for the exporter to authenticate against the Squid proxy itself
- Allow the gathering of process information without requiring root privileges
- The exporter can now be configured using environment variables
- Added support for custom labels to all exported metrics for better data filtering
- New metrics to track if Squid is running (squid_up), how long a scrape takes, and if any errors occurred
- Added 'service time' metrics to analyze proxy speed and performance.
- Added a metric for open file descriptors (process_open_fds) to help prevent connection bottlenecks
- Corrected the squid_client_http_requests_total metric to ensure accurate reporting
golang-github-lusitaniae-apache_exporter:
-
Version update from 1.0.8 to 1.0.10:
- Updated github.com/prometheus/client_golang to 1.21.1
- Updated github.com/prometheus/common to 0.63.0
- Updated github.com/prometheus/exporter-toolkit to 0.14.0
- Fixed signal handler logging
golang-github-prometheus-prometheus:
-
Security issues fixed:
- CVE-2026-27606: Fixed arbitrary file write via path traversal in rollup (bsc#1258893)
- CVE-2026-25547: Fixed unbounded brace range expansion leading to excessive CPU and memory consumption (bsc#1257841)
- CVE-2026-1615, CVE-2025-61140 The old web UI is no longer built due to security issues (bsc#1257897, bsc#1257442)
- CVE-2025-13465: Bump lodash package to version 4.17.23 to fix prototype pollution vulnerability (bsc#1257329)
- CVE-2025-12816: Interpretation conflict vulnerability allowing bypassing cryptographic verifications (bsc#1255588)
-
Version update from 2.53.4 to 3.5.0 with the following highlighted changes (jsc#PED-13824):
- Modernized Interface: Introduced a brand-new UI
- Enhanced Cloud and Auth: Added unified AWS service discovery (EC2, ECS, Lightsail) and Azure Workload Identity support for more secure, native cloudauthentication.
- Performance Standards: Fully integrated OpenTelemetry (OTLP) ingestion and moved Native Histograms from experimental to a stable feature.
- Advanced Data Export: Rolled out Remote Write 2.0, offering better performance and metadata handling when sending data to external systems.
- Query Power: Added new PromQL functions (like first_over_time and last_over_time) and optimization for grouping operations
- Better Visibility: The UI now displays detailed relabeling steps, scrape intervals, and timeouts, making it easier to troubleshoot why targets aren't reporting correctly.
- Critical Fixes: Resolved significant memory leaks related to query logging and fixed bugs where targets were accidentally being scraped multiple times
grafana:
-
Security issues fixed:
- CVE-2026-21722: Public dashboards annotations: use dashboard timerange if time selection disabled (bsc#1258136)
- CVE-2026-21721: Fixed access control by the dashboard permissions API (bsc#1257337)
- CVE-2026-21720: Fixed unauthenticated DoS (bsc#1257349)
- CVE-2025-68156: Fixed potential DoS via unbounded recursion in builtin functions (bsc#1255340)
- CVE-2025-3415: Fixedexposure of DingDing alerting integration URL to Viewer level users (bsc#1245302)
-
Version update from 11.5.10 to 11.6.11 with the following highlighted changes and fixes:
- Performance Boost: Introduced WebGL-powered geomaps for smoother map visualizations and removed blurred backgrounds from UI overlays to speed up the interface *…
- Record
SUSE-SU-2026:1013-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:1037-1 No score
Security update for grafana
This update for grafana fixes the following issues:
-
Security issues fixed:
- CVE-2026-21722: Public dashboards annotations: use dashboard timerange if time selection disabled (bsc#1258136)
- CVE-2026-21721: Fixed access control by the dashboard permissions API (bsc#1257337)
- CVE-2026-21720: Fixed unauthenticated DoS (bsc#1257349)
- CVE-2025-68156: Fixed potential DoS via unbounded recursion in builtin functions (bsc#1255340)
- CVE-2025-3415: Fixed exposure of DingDing alerting integration URL to Viewer level users (bsc#1245302)
-
Version update from 11.5.10 to 11.6.11 with the following highlighted changes and fixes:
- Performance Boost: Introduced WebGL-powered geomaps for smoother map visualizations and removed blurred backgrounds from UI overlays to speed up the interface.
- One-Click Actions: Visualizations now support faster navigation via one-click links and actions.
- Alerting History: Added version history for alert rules, allowing you to track changes over time.
- Service Accounts: Automated the migration of old API keys to more secure Service Accounts upon startup.
- Cron Support: Annotations now support Cron syntax for more flexible scheduling.
- Identity and Auth: Hardened the Avatar feature (now requires sign-in) and fixed several login redirection issues when Grafana is hosted on a subpath.
- Data Source Support: Added support for Cloud Partner Prometheus data sources and improved Azure legend formatting.
- Alerting Limits: Added size limits for expanded notification templates to prevent system strain.
- RBAC: Integrated Role-Based Access Control (RBAC) into the Alertmanager via the reqAction field.
- Data Consistency: Fixed several issues with Graphite and InfluxDB regarding how variables are handled in repeated rows or nested queries.
- Dashboard Reliability: Resolved bugs involving row repeats and 'self-referencing' data links.
- Alerting Fixes: Patched a critical 'panic' (crash) caused by a race condition in alert rules and fixed issues where contact points weren't working correctly.
- URL Handling: Fixed a bug where 'true' values in URL parameters weren't being read correctly
- Record
SUSE-SU-2026:1037-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:20214-1 No score
Security update for alloy
This update for alloy fixes the following issues:
Update to 1.12.2:
Security fixes:
- CVE-2025-68156: github.com/expr-lang/expr/builtin: Fixed potential DoS via unbounded recursion (bsc#1255333):
- CVE-2025-31133, CVE-2025-52565, CVE-2025-52881: github.com/opencontainers/runc: Fixed container breakouts by bypassing runc's restrictions for writing to arbitrary /proc files (bsc#1255074)
Other fixes:
- Add missing configuration parameter
deployment_name_from_replicaset to k8sattributes processor
(5b90a9d) (@dehaansa)
- database_observability: Fix schema_details collector to fetch
column definitions with case sensitive table names (#4872)
(560dff4) (@jharvey10, @fridgepoet)
- deps: Update jose2go to 1.7.0 (#4858) (dfdd341) (@jharvey10)
- deps: Update npm dependencies [backport] (#5201) (8e06c26)
(@jharvey10)
- Ensure the squid exporter wrapper properly brackets ipv6
addresses [backport] (#5205) (e329cc6) (@dehaansa)
- Preserve meta labels in loki.source.podlogs (#5097) (ab4b21e)
(@kalleep)
- Prevent panic in import.git when update fails [backport]
(#5204) (c82fbae) (@dehaansa, @jharvey10)
- show correct fallback alloy version instead of v1.13.0
(#5110) (b72be99) (@dehaansa, @jharvey10)
- Record
SUSE-SU-2026:20214-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/expr-lang/exprGo |
before 1.17.7 | 1.17.7 |
opentelemetry-collectorAlmaLinux:10 |
before 0.135.0-2.el10_1 | 0.135.0-2.el10_1 |
opentelemetry-collectorAlmaLinux:9 |
before 0.135.0-2.el9_7 | 0.135.0-2.el9_7 |
azl-otel-collectorAzure Linux:3 |
through 0.127.0-1 | None known |
corednsAzure Linux:3 |
before 1.11.4-12 | 1.11.4-12 |
kedaAzure Linux:3 |
before 2.14.1-9 | 2.14.1-9 |
opentelemetry-collectorRed Hat:enterprise_linux:10.1 |
before 0:0.135.0-2.el10_1 | 0:0.135.0-2.el10_1 |
opentelemetry-collectorRed Hat:enterprise_linux:9::appstream |
before 0:0.135.0-2.el9_7 | 0:0.135.0-2.el9_7 |
opentelemetry-collectorRed Hat:rhel_eus:9.4::appstream |
before 0:0.135.0-2.el9_4 | 0:0.135.0-2.el9_4 |
opentelemetry-collectorRed Hat:rhel_eus:9.6::appstream |
before 0:0.135.0-2.el9_6 | 0:0.135.0-2.el9_6 |
Show 77 moreShow less
| Package | Affected | Fixed |
|---|---|---|
opentelemetry-collectorRed Hat:enterprise_linux_eus:10.0 |
before 0:0.135.0-2.el10_0 | 0:0.135.0-2.el10_0 |
opentelemetry-collectorRocky Linux:10 |
before 0:0.135.0-2.el10_1 | 0:0.135.0-2.el10_1 |
opentelemetry-collectorRocky Linux:9 |
before 0:0.135.0-2.el9_7 | 0:0.135.0-2.el9_7 |
rootio-github.com/expr-lang/exprRoot:Go |
before v1.16.9-root.io.1 | v1.16.9-root.io.1v1.16.9-root.io.2 |
github.com/expr-lang/exprRoot:Go |
before v1.16.9-aikido.2 | v1.16.9-aikido.2 |
govulncheck-vulndbopenSUSE:Leap 15.6 From an advisory covering 76 CVEs |
before 0.0.20251230T014957-150000.1.134.1 | 0.0.20251230T014957-150000.1.134.1 |
alloySUSE:Linux Enterprise Module for Basesystem 15 SP7 From an advisory covering 4 CVEs |
before 1.12.2-150700.15.15.1 | 1.12.2-150700.15.15.1 |
golang-github-QubitProducts-exporter_exporterSUSE:Multi Linux Manager Tools SLE-12 From an advisory covering 2 CVEs |
before 0.4.0-120002.3.3.1 | 0.4.0-120002.3.3.1 |
golang-github-boynux-squid_exporterSUSE:Multi Linux Manager Tools SLE-12 From an advisory covering 2 CVEs |
before 1.13.0-120002.3.3.1 | 1.13.0-120002.3.3.1 |
golang-github-lusitaniae-apache_exporterSUSE:Multi Linux Manager Tools SLE-12 From an advisory covering 2 CVEs |
before 1.0.10-120002.3.3.1 | 1.0.10-120002.3.3.1 |
golang-github-prometheus-alertmanagerSUSE:Multi Linux Manager Tools SLE-12 From an advisory covering 2 CVEs |
before 0.28.1-120002.4.6.1 | 0.28.1-120002.4.6.1 |
golang-github-prometheus-node_exporterSUSE:Multi Linux Manager Tools SLE-12 From an advisory covering 2 CVEs |
before 1.9.1-120002.3.3.1 | 1.9.1-120002.3.3.1 |
golang-github-prometheus-prometheusSUSE:Multi Linux Manager Tools SLE-12 From an advisory covering 2 CVEs |
before 3.5.0-120002.3.3.1 | 3.5.0-120002.3.3.1 |
grafanaSUSE:Multi Linux Manager Tools SLE-12 From an advisory covering 2 CVEs |
before 11.5.10-120002.4.9.1 | 11.5.10-120002.4.9.1 |
mgr-pushSUSE:Multi Linux Manager Tools SLE-12 From an advisory covering 2 CVEs |
before 5.1.5-120002.3.6.1 | 5.1.5-120002.3.6.1 |
prometheus-blackbox_exporterSUSE:Multi Linux Manager Tools SLE-12 From an advisory covering 2 CVEs |
before 0.26.0-120002.3.3.1 | 0.26.0-120002.3.3.1 |
rhnlibSUSE:Multi Linux Manager Tools SLE-12 From an advisory covering 2 CVEs |
before 5.1.4-120002.3.6.1 | 5.1.4-120002.3.6.1 |
spacecmdSUSE:Multi Linux Manager Tools SLE-12 From an advisory covering 2 CVEs |
before 5.1.12-120002.3.6.1 | 5.1.12-120002.3.6.1 |
spacewalk-client-toolsSUSE:Multi Linux Manager Tools SLE-12 From an advisory covering 2 CVEs |
before 5.1.8-120002.3.6.1 | 5.1.8-120002.3.6.1 |
supportutils-plugin-susemanager-clientSUSE:Multi Linux Manager Tools SLE-12 From an advisory covering 2 CVEs |
before 5.1.5-120002.3.6.1 | 5.1.5-120002.3.6.1 |
uyuni-common-libsSUSE:Multi Linux Manager Tools SLE-12 From an advisory covering 2 CVEs |
before 5.1.5-120002.3.3.1 | 5.1.5-120002.3.3.1 |
uyuni-toolsSUSE:Multi Linux Manager Tools SLE-12 From an advisory covering 2 CVEs |
before 5.1.24-120002.3.9.1 | 5.1.24-120002.3.9.1 |
dracut-saltbootSUSE:Multi Linux Manager Tools SLE-15 From an advisory covering 2 CVEs |
before 1.1.0-150002.3.6.1 | 1.1.0-150002.3.6.1 |
golang-github-QubitProducts-exporter_exporterSUSE:Multi Linux Manager Tools SLE-15 From an advisory covering 2 CVEs |
before 0.4.0-150002.3.3.1 | 0.4.0-150002.3.3.1 |
golang-github-boynux-squid_exporterSUSE:Multi Linux Manager Tools SLE-15 From an advisory covering 2 CVEs |
before 1.13.0-150002.3.3.1 | 1.13.0-150002.3.3.1 |
golang-github-lusitaniae-apache_exporterSUSE:Multi Linux Manager Tools SLE-15 From an advisory covering 2 CVEs |
before 1.0.10-150002.3.3.1 | 1.0.10-150002.3.3.1 |
golang-github-prometheus-alertmanagerSUSE:Multi Linux Manager Tools SLE-15 From an advisory covering 2 CVEs |
before 0.28.1-150002.4.6.1 | 0.28.1-150002.4.6.1 |
golang-github-prometheus-node_exporterSUSE:Multi Linux Manager Tools SLE-15 From an advisory covering 2 CVEs |
before 1.9.1-150002.3.3.1 | 1.9.1-150002.3.3.1 |
golang-github-prometheus-prometheusSUSE:Multi Linux Manager Tools SLE-15 From an advisory covering 2 CVEs |
before 3.5.0-150002.3.3.1 | 3.5.0-150002.3.3.1 |
grafanaSUSE:Multi Linux Manager Tools SLE-15 From an advisory covering 2 CVEs |
before 11.5.10-150002.4.9.1 | 11.5.10-150002.4.9.1 |
mgr-pushSUSE:Multi Linux Manager Tools SLE-15 From an advisory covering 2 CVEs |
before 5.1.5-150002.3.6.2 | 5.1.5-150002.3.6.2 |
prometheus-blackbox_exporterSUSE:Multi Linux Manager Tools SLE-15 From an advisory covering 2 CVEs |
before 0.26.0-150002.3.3.1 | 0.26.0-150002.3.3.1 |
rhnlibSUSE:Multi Linux Manager Tools SLE-15 From an advisory covering 2 CVEs |
before 5.1.4-150002.3.6.1 | 5.1.4-150002.3.6.1 |
spacecmdSUSE:Multi Linux Manager Tools SLE-15 From an advisory covering 2 CVEs |
before 5.1.12-150002.3.6.1 | 5.1.12-150002.3.6.1 |
spacewalk-client-toolsSUSE:Multi Linux Manager Tools SLE-15 From an advisory covering 2 CVEs |
before 5.1.8-150002.3.6.1 | 5.1.8-150002.3.6.1 |
supportutils-plugin-susemanager-clientSUSE:Multi Linux Manager Tools SLE-15 From an advisory covering 2 CVEs |
before 5.1.5-150002.3.6.1 | 5.1.5-150002.3.6.1 |
uyuni-common-libsSUSE:Multi Linux Manager Tools SLE-15 From an advisory covering 2 CVEs |
before 5.1.5-150002.3.3.1 | 5.1.5-150002.3.3.1 |
uyuni-toolsSUSE:Multi Linux Manager Tools SLE-15 From an advisory covering 2 CVEs |
before 5.1.24-150002.3.9.1 | 5.1.24-150002.3.9.1 |
dracut-saltbootSUSE:Multi Linux Manager Tools SLE-Micro-5 From an advisory covering 2 CVEs |
before 1.1.0-150002.3.6.1 | 1.1.0-150002.3.6.1 |
golang-github-QubitProducts-exporter_exporterSUSE:Multi Linux Manager Tools SLE-Micro-5 From an advisory covering 2 CVEs |
before 0.4.0-150002.3.3.1 | 0.4.0-150002.3.3.1 |
golang-github-prometheus-node_exporterSUSE:Multi Linux Manager Tools SLE-Micro-5 From an advisory covering 2 CVEs |
before 1.9.1-150002.3.3.1 | 1.9.1-150002.3.3.1 |
prometheus-blackbox_exporterSUSE:Multi Linux Manager Tools SLE-Micro-5 From an advisory covering 2 CVEs |
before 0.26.0-150002.3.3.1 | 0.26.0-150002.3.3.1 |
uyuni-toolsSUSE:Multi Linux Manager Tools SLE-Micro-5 From an advisory covering 2 CVEs |
before 5.1.24-150002.3.9.1 | 5.1.24-150002.3.9.1 |
dracut-saltbootSUSE:Manager Client Tools 15 From an advisory covering 11 CVEs |
before 1.1.0-150000.1.65.1 | 1.1.0-150000.1.65.1 |
golang-github-QubitProducts-exporter_exporterSUSE:Manager Client Tools 15 From an advisory covering 11 CVEs |
before 0.4.0-150000.1.21.1 | 0.4.0-150000.1.21.1 |
golang-github-boynux-squid_exporterSUSE:Manager Client Tools 15 From an advisory covering 11 CVEs |
before 1.13.0-150000.1.12.1 | 1.13.0-150000.1.12.1 |
golang-github-lusitaniae-apache_exporterSUSE:Manager Client Tools 15 From an advisory covering 11 CVEs |
before 1.0.10-150000.1.26.1 | 1.0.10-150000.1.26.1 |
golang-github-prometheus-prometheusSUSE:Manager Client Tools 15 From an advisory covering 11 CVEs |
before 3.5.0-150000.3.67.1 | 3.5.0-150000.3.67.1 |
grafanaSUSE:Manager Client Tools 15 From an advisory covering 11 CVEs |
before 11.6.11-150000.1.90.1 | 11.6.11-150000.1.90.1 |
prometheus-blackbox_exporterSUSE:Manager Client Tools 15 From an advisory covering 11 CVEs |
before 0.26.0-150000.1.30.2 | 0.26.0-150000.1.30.2 |
spacecmdSUSE:Manager Client Tools 15 From an advisory covering 11 CVEs |
before 5.0.15-150000.3.142.1 | 5.0.15-150000.3.142.1 |
uyuni-toolsSUSE:Manager Client Tools 15 From an advisory covering 11 CVEs |
before 0.1.38-150000.1.30.1 | 0.1.38-150000.1.30.1 |
dracut-saltbootSUSE:Manager Client Tools for SLE Micro 5 From an advisory covering 11 CVEs |
before 1.1.0-150000.1.65.1 | 1.1.0-150000.1.65.1 |
golang-github-QubitProducts-exporter_exporterSUSE:Manager Client Tools for SLE Micro 5 From an advisory covering 11 CVEs |
before 0.4.0-150000.1.21.1 | 0.4.0-150000.1.21.1 |
prometheus-blackbox_exporterSUSE:Manager Client Tools for SLE Micro 5 From an advisory covering 11 CVEs |
before 0.26.0-150000.1.30.2 | 0.26.0-150000.1.30.2 |
uyuni-toolsSUSE:Manager Client Tools for SLE Micro 5 From an advisory covering 11 CVEs |
before 0.1.38-150000.1.30.1 | 0.1.38-150000.1.30.1 |
golang-github-prometheus-promuSUSE:Linux Enterprise Module for Package Hub 15 SP7 From an advisory covering 11 CVEs |
before 0.17.0-150000.3.30.1 | 0.17.0-150000.3.30.1 |
dracut-saltbootopenSUSE:Leap 15.6 From an advisory covering 11 CVEs |
before 1.1.0-150000.1.65.1 | 1.1.0-150000.1.65.1 |
golang-github-QubitProducts-exporter_exporteropenSUSE:Leap 15.6 From an advisory covering 11 CVEs |
before 0.4.0-150000.1.21.1 | 0.4.0-150000.1.21.1 |
golang-github-boynux-squid_exporteropenSUSE:Leap 15.6 From an advisory covering 11 CVEs |
before 1.13.0-150000.1.12.1 | 1.13.0-150000.1.12.1 |
golang-github-lusitaniae-apache_exporteropenSUSE:Leap 15.6 From an advisory covering 11 CVEs |
before 1.0.10-150000.1.26.1 | 1.0.10-150000.1.26.1 |
golang-github-prometheus-promuopenSUSE:Leap 15.6 From an advisory covering 11 CVEs |
before 0.17.0-150000.3.30.1 | 0.17.0-150000.3.30.1 |
prometheus-blackbox_exporteropenSUSE:Leap 15.6 From an advisory covering 11 CVEs |
before 0.26.0-150000.1.30.2 | 0.26.0-150000.1.30.2 |
spacecmdopenSUSE:Leap 15.6 From an advisory covering 11 CVEs |
before 5.0.15-150000.3.142.1 | 5.0.15-150000.3.142.1 |
grafanaSUSE:Linux Enterprise Module for Package Hub 15 SP7 From an advisory covering 5 CVEs |
before 11.6.11-150200.3.83.1 | 11.6.11-150200.3.83.1 |
grafanaopenSUSE:Leap 15.6 From an advisory covering 5 CVEs |
before 11.6.11-150200.3.83.1 | 11.6.11-150200.3.83.1 |
alloySUSE:Linux Enterprise Server 16.0 From an advisory covering 4 CVEs |
before 1.12.2-160000.1.1 | 1.12.2-160000.1.1 |
alloySUSE:Linux Enterprise Server for SAP applications 16.0 From an advisory covering 4 CVEs |
before 1.12.2-160000.1.1 | 1.12.2-160000.1.1 |
coredns-for-k8s1.33openSUSE:Tumbleweed |
before 1.12.0-2.1 | 1.12.0-2.1 |
coredns-for-k8s1.34openSUSE:Tumbleweed |
before 1.12.1-2.1 | 1.12.1-2.1 |
coredns-for-k8s1.35openSUSE:Tumbleweed |
before 1.13.1-2.1 | 1.13.1-2.1 |
corednsopenSUSE:Tumbleweed |
before 1.14.0-1.1 | 1.14.0-1.1 |
grafanaopenSUSE:Tumbleweed |
before 11.6.7-2.1 | 11.6.7-2.1 |
alloyopenSUSE:Tumbleweed From an advisory covering 2 CVEs |
before 1.12.2-2.1 | 1.12.2-2.1 |
corednsopenSUSE:Leap 16.0 From an advisory covering 4 CVEs |
before 1.14.0-bp160.1.1 | 1.14.0-bp160.1.1 |
alloyopenSUSE:Leap 16.0 From an advisory covering 4 CVEs |
before 1.12.2-160000.1.1 | 1.12.2-160000.1.1 |
govulncheck-vulndbopenSUSE:Leap 16.0 From an advisory covering 1734 CVEs |
before 0.0.20260723T184607-160000.1.1 | 0.0.20260723T184607-160000.1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected | ||
| facts | OSV | |
| affected | ||
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2025-68156 is a high vulnerability (CVSS 7.5) in Expr-lang Expr, published December 16, 2025. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.42%, the 36th percentile. Fixed in github.com/expr-lang/expr 1.17.7.
References
github.com/expr-lang/expr/security/advisories/GHSA-cfpf-hrx2-8rv6
github.com/expr-lang/expr/pull/870
nvd.nist.gov/vuln/detail/CVE-2025-68156
github.com/advisories/GHSA-cfpf-hrx2-8rv6
access.redhat.com/errata/RHSA-2025:23664
access.redhat.com/security/cve/CVE-2025-68156
Show 194 moreShow less
bugzilla.redhat.com/2422891
errata.almalinux.org/10/ALSA-2025-23664.html
access.redhat.com/errata/RHSA-2025:23729
errata.almalinux.org/9/ALSA-2025-23729.html
github.com/CVEProject/cvelistV5/tree/main/cves/2025/68xxx/CVE-2025-68156.json
security-tracker.debian.org/tracker/CVE-2025-68156
github.com/expr-lang/expr
access.redhat.com/security/updates/classification
bugzilla.redhat.com/show_bug.cgi?id=2422891
security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_23664.json
cve.org/CVERecord?id=CVE-2025-68156
security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_23729.json
access.redhat.com/errata/RHSA-2026:0512
security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_0512.json
access.redhat.com/errata/RHSA-2026:0513
security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_0513.json
access.redhat.com/errata/RHSA-2026:0514
security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_0514.json
errata.rockylinux.org/RLSA-2025:23664
errata.rockylinux.org/RLSA-2025:23729
suse.com/support/update/announcement/2026/suse-su-20260037-1
suse.com/security/cve/CVE-2017-18874
suse.com/security/cve/CVE-2017-18878
suse.com/security/cve/CVE-2017-18885
suse.com/security/cve/CVE-2017-18886
suse.com/security/cve/CVE-2017-18887
suse.com/security/cve/CVE-2017-18888
suse.com/security/cve/CVE-2017-18889
suse.com/security/cve/CVE-2017-18890
suse.com/security/cve/CVE-2024-41260
suse.com/security/cve/CVE-2024-41265
suse.com/security/cve/CVE-2024-44905
suse.com/security/cve/CVE-2025-0426
suse.com/security/cve/CVE-2025-10543
suse.com/security/cve/CVE-2025-11393
suse.com/security/cve/CVE-2025-11777
suse.com/security/cve/CVE-2025-12419
suse.com/security/cve/CVE-2025-12421
suse.com/security/cve/CVE-2025-12559
suse.com/security/cve/CVE-2025-12689
suse.com/security/cve/CVE-2025-13281
suse.com/security/cve/CVE-2025-13324
suse.com/security/cve/CVE-2025-13352
suse.com/security/cve/CVE-2025-13870
suse.com/security/cve/CVE-2025-13888
suse.com/security/cve/CVE-2025-14764
suse.com/security/cve/CVE-2025-34410
suse.com/security/cve/CVE-2025-34429
suse.com/security/cve/CVE-2025-34430
suse.com/security/cve/CVE-2025-47913
suse.com/security/cve/CVE-2025-54410
suse.com/security/cve/CVE-2025-60633
suse.com/security/cve/CVE-2025-62155
suse.com/security/cve/CVE-2025-62190
suse.com/security/cve/CVE-2025-64521
suse.com/security/cve/CVE-2025-64702
suse.com/security/cve/CVE-2025-64708
suse.com/security/cve/CVE-2025-64715
suse.com/security/cve/CVE-2025-65637
suse.com/security/cve/CVE-2025-65754
suse.com/security/cve/CVE-2025-65795
suse.com/security/cve/CVE-2025-65796
suse.com/security/cve/CVE-2025-65797
suse.com/security/cve/CVE-2025-65798
suse.com/security/cve/CVE-2025-65799
suse.com/security/cve/CVE-2025-65942
suse.com/security/cve/CVE-2025-66001
suse.com/security/cve/CVE-2025-66490
suse.com/security/cve/CVE-2025-66491
suse.com/security/cve/CVE-2025-66507
suse.com/security/cve/CVE-2025-66508
suse.com/security/cve/CVE-2025-66565
suse.com/security/cve/CVE-2025-66626
suse.com/security/cve/CVE-2025-67488
suse.com/security/cve/CVE-2025-67494
suse.com/security/cve/CVE-2025-67495
suse.com/security/cve/CVE-2025-67499
suse.com/security/cve/CVE-2025-67508
suse.com/security/cve/CVE-2025-67713
suse.com/security/cve/CVE-2025-67717
suse.com/security/cve/CVE-2025-67818
suse.com/security/cve/CVE-2025-67819
suse.com/security/cve/CVE-2025-68113
suse.com/security/cve/CVE-2025-68120
suse.com/security/cve/CVE-2025-68156
suse.com/security/cve/CVE-2025-68274
suse.com/security/cve/CVE-2025-68476
suse.com/security/cve/CVE-2025-68938
suse.com/security/cve/CVE-2025-68939
suse.com/security/cve/CVE-2025-68940
suse.com/security/cve/CVE-2025-68941
suse.com/security/cve/CVE-2025-68942
suse.com/security/cve/CVE-2025-68943
suse.com/security/cve/CVE-2025-68944
suse.com/security/cve/CVE-2025-68945
suse.com/security/cve/CVE-2025-68946
suse.com/security/cve/CVE-2025-8110
suse.com/support/update/announcement/2026/suse-su-20260327-1
bugzilla.suse.com/1255074
bugzilla.suse.com/1255333
suse.com/security/cve/CVE-2025-31133
suse.com/security/cve/CVE-2025-52565
suse.com/security/cve/CVE-2025-52881
suse.com/support/update/announcement/2026/suse-su-20260628-1
bugzilla.suse.com/1227579
bugzilla.suse.com/1247644
bugzilla.suse.com/1247721
bugzilla.suse.com/1248848
bugzilla.suse.com/1249400
bugzilla.suse.com/1249532
bugzilla.suse.com/1250940
bugzilla.suse.com/1250976
bugzilla.suse.com/1250981
bugzilla.suse.com/1251044
bugzilla.suse.com/1251138
bugzilla.suse.com/1251995
bugzilla.suse.com/1253174
bugzilla.suse.com/1253282
bugzilla.suse.com/1253347
bugzilla.suse.com/1253659
bugzilla.suse.com/1253738
bugzilla.suse.com/1253966
bugzilla.suse.com/1254478
bugzilla.suse.com/1255340
bugzilla.suse.com/1255588
bugzilla.suse.com/1255781
suse.com/security/cve/CVE-2025-12816
suse.com/support/update/announcement/2026/suse-su-20260630-1
bugzilla.suse.com/1253004
suse.com/support/update/announcement/2026/suse-su-20261013-1
bugzilla.suse.com/1245302
bugzilla.suse.com/1254589
bugzilla.suse.com/1256803
bugzilla.suse.com/1257329
bugzilla.suse.com/1257337
bugzilla.suse.com/1257349
bugzilla.suse.com/1257442
bugzilla.suse.com/1257841
bugzilla.suse.com/1257897
bugzilla.suse.com/1257941
bugzilla.suse.com/1258136
bugzilla.suse.com/1258893
suse.com/security/cve/CVE-2025-13465
suse.com/security/cve/CVE-2025-3415
suse.com/security/cve/CVE-2025-61140
suse.com/security/cve/CVE-2026-1615
suse.com/security/cve/CVE-2026-21720
suse.com/security/cve/CVE-2026-21721
suse.com/security/cve/CVE-2026-21722
suse.com/security/cve/CVE-2026-25547
suse.com/security/cve/CVE-2026-27606
suse.com/support/update/announcement/2026/suse-su-20261037-1
suse.com/support/update/announcement/2026/suse-su-202620214-1
bugzilla.suse.com/1239294
bugzilla.suse.com/1239728
bugzilla.suse.com/1249389
bugzilla.suse.com/1255345
bugzilla.suse.com/1256411
suse.com/security/cve/CVE-2024-51744
suse.com/security/cve/CVE-2025-58063
suse.com/security/cve/CVE-2025-68161
bugzilla.suse.com/1231844
bugzilla.suse.com/1232975
bugzilla.suse.com/1233343
bugzilla.suse.com/1235206
bugzilla.suse.com/1235574
bugzilla.suse.com/1236510
bugzilla.suse.com/1236559
bugzilla.suse.com/1236734
bugzilla.suse.com/1237671
bugzilla.suse.com/1238703
bugzilla.suse.com/1241683
bugzilla.suse.com/1241687
bugzilla.suse.com/1241809
bugzilla.suse.com/1243672
bugzilla.suse.com/1243714
bugzilla.suse.com/1246735
bugzilla.suse.com/1246736
bugzilla.suse.com/1250616
bugzilla.suse.com/1251454
bugzilla.suse.com/1251657
bugzilla.suse.com/1254113
suse.com/security/cve/CVE-2023-45288
suse.com/security/cve/CVE-2024-11741
suse.com/security/cve/CVE-2024-28180
suse.com/security/cve/CVE-2024-45339
suse.com/security/cve/CVE-2024-9264
suse.com/security/cve/CVE-2024-9476
suse.com/security/cve/CVE-2025-11065
suse.com/security/cve/CVE-2025-21613
suse.com/security/cve/CVE-2025-22870
suse.com/security/cve/CVE-2025-22872
suse.com/security/cve/CVE-2025-2703
suse.com/security/cve/CVE-2025-27144
Left out here: 1,658 references and the rest of 7 source descriptions. The JSON record has them.