BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-33186High confidence

gRPC-Go has an authorization bypass via missing leading slash in :path

grpc · grpc-go

Official source article: GitHub GHSA-P77J-4MVH-X3M3 ↗. Check the applicable product and release in the original source.

9.1CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 1.63% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs grpc grpc-go and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

6 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcegolang-google-grpcAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcegolang-google-grpcAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcegolang-google-grpcVendor fix publishedDebian records a fixed source-package version for this release.1.79.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcegolang-google-grpcVendor fix publishedDebian records a fixed source-package version for this release.1.79.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · esm-appsgolang-google-grpcUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivegoogle-guest-agentUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges2 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Gogoogle.golang.org/grpcSEMVER: introduced 0; fixed 1.79.31.79.3OSV record ↗aggregator derived · 10 Sep 2026
gogoogle.golang.org/grpc< 1.79.31.79.3GitHub advisory ↗upstream repository advisory · 25 Mar 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-13830

No EUVD known-exploited evidence

gRPC-Go is the Go language implementation of gRPC. Versions prior to 1.79.3 have an authorization bypass resulting from improper input validation of the HTTP/2 `:path` pseudo-header. The gRPC-Go server was too lenient in its routing logic, accepting requests where the `:path` omitted the mandatory leading slash (e.g., `Service/Method` instead of `/Service/Method`). While the server successfully routed these requests to the correct handler, authorization interceptors (including the official `grpc/authz` package) evaluated the raw, non-canonical path string. Consequently, "deny" rules defined using canonical paths (starting with `/`) failed to match the incoming request, allowing it to bypass the policy if a fallback "allow" rule was present. This affects gRPC-Go servers that use path-based authorization interceptors, such as the official RBAC implementation in `google.golang.org/grpc/authz` or custom interceptors relying on `info.FullMethod` or `grpc.Method(ctx)`; AND that have a security policy contains specific "deny" rules for canonical paths but allows other requests by default (a fallback "allow" rule). The vulnerability is exploitable by an attacker who can send raw HTTP/2 frames with malformed `:path` headers directly to the gRPC server. The fix in version 1.79.3 ensures that any request with a `:path` that does not start with a leading slash is immediately rejected with a `codes.Unimplemented` error, preventing it from reaching authorization interceptors or handlers with a non-canonical path string. While upgrading is the most secure and recommended path, users can mitigate the vulnerability using one of the following methods: Use a validating interceptor (recommended mitigation); infrastructure-level normalization; and/or policy hardening.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
9.1 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

gRPC-Go is the Go language implementation of gRPC. Versions prior to 1.79.3 have an authorization bypass resulting from improper input validation of the HTTP/2 `:path` pseudo-header. The gRPC-Go server was too lenient in its routing logic, accepting requests where the `:path` omitted the mandatory leading slash (e.g., `Service/Method` instead of `/Service/Method`). While the server successfully routed these requests to the correct handler, authorization interceptors (including the official `grpc/authz` package) evaluated the raw, non-canonical path string. Consequently, "deny" rules defined using canonical paths (starting with `/`) failed to match the incoming request, allowing it to bypass the policy if a fallback "allow" rule was present. This affects gRPC-Go servers that use path-based authorization interceptors, such as the official RBAC implementation in `google.golang.org/grpc/authz` or custom interceptors relying on `info.FullMethod` or `grpc.Method(ctx)`; AND that have a security policy contains specific "deny" rules for canonical paths but allows other requests by default (a fallback "allow" rule). The vulnerability is exploitable by an attacker who can send raw HTTP/2 frames with malformed `:path` headers directly to the gRPC server. The fix in version 1.79.3 ensures that any request with a `:path` that does not start with a leading slash is immediately rejected with a `codes.Unimplemented` error, preventing it from reaching authorization interceptors or handlers with a non-canonical path string. While upgrading is the most secure and recommended path, users can mitigate the vulnerability using one of the following methods: Use a validating interceptor (recommended mitigation); infrastructure-level normalization; and/or policy hardening.

What

gRPC-Go is the Go language implementation of gRPC. Versions prior to 1.79.3 have an authorization bypass resulting from improper input validation of the HTTP/2 `:path` pseudo-header. The gRPC-Go server was too lenient in its routing logic, accepting requests where the `:path` omitted the mandatory leading slash (e.g., `Service/Method` instead of `/Service/Method`). While the server successfully routed these requests to the correct handler, authorization interceptors (including the official `grpc/authz` package) evaluated the raw, non-canonical path string. Consequently, "deny" rules defined using canonical paths (starting with `/`) failed to match the incoming request, allowing it to bypass the policy if a fallback "allow" rule was present. This affects gRPC-Go servers that use path-based authorization interceptors, such as the official RBAC implementation in `google.golang.org/grpc/authz` or custom interceptors relying on `info.FullMethod` or `grpc.Method(ctx)`; AND that have a security policy contains specific "deny" rules for canonical paths but allows other requests by default (a fallback "allow" rule). The vulnerability is exploitable by an attacker who can send raw HTTP/2 frames with malformed `:path` headers directly to the gRPC server. The fix in version 1.79.3 ensures that any request with a `:path` that does not start with a leading slash is immediately rejected with a `codes.Unimplemented` error, preventing it from reaching authorization interceptors or handlers with a non-canonical path string. While upgrading is the most secure and recommended path, users can mitigate the vulnerability using one of the following methods: Use a validating interceptor (recommended mitigation); infrastructure-level normalization; and/or policy hardening.

Why

The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

gRPC-Go is the Go language implementation of gRPC. Versions prior to 1.79.3 have an authorization bypass resulting from improper input validation of the HTTP/2 `:path` pseudo-header. The gRPC-Go server was too lenient in its routing logic, accepting requests where the `:path` omitted the mandatory leading slash (e.g., `Service/Method` instead of `/Service/Method`). While the server successfully routed these requests to the correct handler, authorization interceptors (including the official `grpc/authz` package) evaluated the raw, non-canonical path string. Consequently, "deny" rules defined using canonical paths (starting with `/`) failed to match the incoming request, allowing it to bypass the policy if a fallback "allow" rule was present. This affects gRPC-Go servers that use path-based authorization interceptors, such as the official RBAC implementation in `google.golang.org/grpc/authz` or custom interceptors relying on `info.FullMethod` or `grpc.Method(ctx)`; AND that have a security policy contains specific "deny" rules for canonical paths but allows other requests by default (a fallback "allow" rule). The vulnerability is exploitable by an attacker who can send raw HTTP/2 frames with malformed `:path` headers directly to the gRPC server. The fix in version 1.79.3 ensures that any request with a `:path` that does not start with a leading slash is immediately rejected with a `codes.Unimplemented` error, preventing it from reaching authorization interceptors or handlers with a non-canonical path string. While upgrading is the most secure and recommended path, users can mitigate the vulnerability using one of the following methods: Use a validating interceptor (recommended mitigation); infrastructure-level normalization; and/or policy hardening.

Why

The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Authorization → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-285 ↗

CWE-285: Improper Authorization. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-285
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-13830Official EUVD mapping

gRPC-Go is the Go language implementation of gRPC. Versions prior to 1.79.3 have an authorization bypass resulting from improper input validation of the HTTP/2 `:path` pseudo-header. The gRPC-Go server was too lenient in its routing logic, accepting requests where the `:path` omitted the mandatory leading slash (e.g., `Service/Method` instead of `/Service/Method`). While the server successfully routed these requests to the correct handler, authorization interceptors (including the official `grpc/authz` package) evaluated the raw, non-canonical path string. Consequently, "deny" rules defined using canonical paths (starting with `/`) failed to match the incoming request, allowing it to bypass the policy if a fallback "allow" rule was present. This affects gRPC-Go servers that use path-based authorization interceptors, such as the official RBAC implementation in `google.golang.org/grpc/authz` or custom interceptors relying on `info.FullMethod` or `grpc.Method(ctx)`; AND that have a security policy contains specific "deny" rules for canonical paths but allows other requests by default (a fallback "allow" rule). The vulnerability is exploitable by an attacker who can send raw HTTP/2 frames with malformed `:path` headers directly to the gRPC server. The fix in version 1.79.3 ensures that any request with a `:path` that does not start with a leading slash is immediately rejected with a `codes.Unimplemented` error, preventing it from reaching authorization interceptors or handlers with a non-canonical path string. While upgrading is the most secure and recommended path, users can mitigate the vulnerability using one of the following methods: Use a validating interceptor (recommended mitigation); infrastructure-level normalization; and/or policy hardening.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3046IBM Concert: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Concert ausnutzen, um beliebigen Programmcode auszuführen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen, um einen SQL-Injection Angriff durchzuführen und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2026-2929Splunk Splunk Enterprise: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Splunk Splunk Enterprise ausnutzen, um beliebigen Code auszuführen, Berechtigungen zu erweitern, Sicherheitsmaßnahmen zu umgehen, SQL-Injection-, serverseitige Request-Forgery- und Cross-Site-Scripting-Angriffe durchzuführen, sensible Informationen offenzulegen oder zu manipulieren, Denial-of-Service-Zustände auszulösen oder andere, nicht näher spezifizierte Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-2894Oracle Fusion Middleware: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Fusion Middleware ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-2451Oracle Siebel CRM: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Siebel CRM ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-1752IBM Business Automation Workflow: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Business Automation Workflow ausnutzen, um Sicherheitsvorkehrungen zu umgehen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, und um einen Cross-Site Scripting Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-1136Red Hat OpenShift Container Platform (gRPC-Go): Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen

Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in Red Hat OpenShift Container Platform ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260325Security Bulletin 25 Mar 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 25 Mar 2026, published on 25 March 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1249Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2026-29181 Référence CVE CVE-2026-3219 https://www.cve.org/CVERecord?id=CVE-2026-3219 Référence CVE CVE-2026-32280 https://www.cve.org/CVERecord?id=CVE-2026-32280 Référence CVE CVE-2026-32281 https://www.cve.org/CVERecord?id=CVE-2026-32281 Référence CVE CVE-2026-32282 https://www.cve.org/CVERecord?id=CVE-2026-32282 Référence CVE CVE-2026-32283 https://www.cve.org/CVERecord?id=CVE-2026-32283 Référence CVE CVE-2026-32288 https://www.cve.org/CVERecord?id=CVE-2026-32288 Référence CVE CVE-2026-32289 https://www.cve.org/CVERecord?id=CVE-2026-32289 Référence CVE CVE-2026-32952 https://www.cve.org/CVERecord?id=CVE-2026-32952 Référence CVE CVE-2026-33186 https://www.cve.org/CVERecord?id=CVE-2026-33186 Référence CVE CVE-2026-33810 https://www.cve.org/CVERecord?id=CVE-2026-33810 Référence CVE CVE-2026-33811 https://www.cve.org/CVERecord?id=CVE-2026-33811 Référence CVE CVE-2026-33814 https://www.cve.org/CVERecord?id=CVE-2026-33814 Référence CVE CVE-2026-33815 https://www.cve.org/CVERecord?id=CVE-2026-33815 Référence CVE CVE-2026-33816 https://www.cve.org/CVERecord?id=CVE-2026-33816 Référence CVE CVE-2026-33818 https://www.cve.org/CVERecord?id=CVE-2026-33818 Référence CVE CVE-2026-34180 https://www.cve.org/CVERecord?id=CVE-2026-34180 Référence CVE CVE-2026-34181 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1056Multiples vulnérabilités dans les produits Splunk

d?id=CVE-2026-31898 Référence CVE CVE-2026-31938 https://www.cve.org/CVERecord?id=CVE-2026-31938 Référence CVE CVE-2026-31958 https://www.cve.org/CVERecord?id=CVE-2026-31958 Référence CVE CVE-2026-32141 https://www.cve.org/CVERecord?id=CVE-2026-32141 Référence CVE CVE-2026-32280 https://www.cve.org/CVERecord?id=CVE-2026-32280 Référence CVE CVE-2026-32281 https://www.cve.org/CVERecord?id=CVE-2026-32281 Référence CVE CVE-2026-32283 https://www.cve.org/CVERecord?id=CVE-2026-32283 Référence CVE CVE-2026-32597 https://www.cve.org/CVERecord?id=CVE-2026-32597 Référence CVE CVE-2026-32647 https://www.cve.org/CVERecord?id=CVE-2026-32647 Référence CVE CVE-2026-33186 https://www.cve.org/CVERecord?id=CVE-2026-33186 Référence CVE CVE-2026-33228 https://www.cve.org/CVERecord?id=CVE-2026-33228 Référence CVE CVE-2026-33532 https://www.cve.org/CVERecord?id=CVE-2026-33532 Référence CVE CVE-2026-33671 https://www.cve.org/CVERecord?id=CVE-2026-33671 Référence CVE CVE-2026-33672 https://www.cve.org/CVERecord?id=CVE-2026-33672 Référence CVE CVE-2026-33750 https://www.cve.org/CVERecord?id=CVE-2026-33750 Référence CVE CVE-2026-33810 https://www.cve.org/CVERecord?id=CVE-2026-33810 Référence CVE CVE-2026-34180 https://www.cve.org/CVERecord?id=CVE-2026-34180 Référence CVE CVE-2026-34513 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0641Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-27142 Référence CVE CVE-2026-27903 https://www.cve.org/CVERecord?id=CVE-2026-27903 Référence CVE CVE-2026-27904 https://www.cve.org/CVERecord?id=CVE-2026-27904 Référence CVE CVE-2026-29045 https://www.cve.org/CVERecord?id=CVE-2026-29045 Référence CVE CVE-2026-29063 https://www.cve.org/CVERecord?id=CVE-2026-29063 Référence CVE CVE-2026-29087 https://www.cve.org/CVERecord?id=CVE-2026-29087 Référence CVE CVE-2026-31958 https://www.cve.org/CVERecord?id=CVE-2026-31958 Référence CVE CVE-2026-32141 https://www.cve.org/CVERecord?id=CVE-2026-32141 Référence CVE CVE-2026-32597 https://www.cve.org/CVERecord?id=CVE-2026-32597 Référence CVE CVE-2026-33186 https://www.cve.org/CVERecord?id=CVE-2026-33186 Référence CVE CVE-2026-33228 https://www.cve.org/CVERecord?id=CVE-2026-33228 Référence CVE CVE-2026-33671 https://www.cve.org/CVERecord?id=CVE-2026-33671 Référence CVE CVE-2026-33672 https://www.cve.org/CVERecord?id=CVE-2026-33672 Référence CVE CVE-2026-33750 https://www.cve.org/CVERecord?id=CVE-2026-33750 Référence CVE CVE-2026-34268 https://www.cve.org/CVERecord?id=CVE-2026-34268 Référence CVE CVE-2026-34282 https://www.cve.org/CVERecord?id=CVE-2026-34282 Référence CVE CVE-2026-35554 https://www.cve.org/CVERecord?id=CVE-2026-35554 Référence CVE CVE-2026-35611 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0627Multiples vulnérabilités dans les produits Splunk

d?id=CVE-2026-32282 Référence CVE CVE-2026-32283 https://www.cve.org/CVERecord?id=CVE-2026-32283 Référence CVE CVE-2026-32288 https://www.cve.org/CVERecord?id=CVE-2026-32288 Référence CVE CVE-2026-32289 https://www.cve.org/CVERecord?id=CVE-2026-32289 Référence CVE CVE-2026-32776 https://www.cve.org/CVERecord?id=CVE-2026-32776 Référence CVE CVE-2026-32777 https://www.cve.org/CVERecord?id=CVE-2026-32777 Référence CVE CVE-2026-32778 https://www.cve.org/CVERecord?id=CVE-2026-32778 Référence CVE CVE-2026-33055 https://www.cve.org/CVERecord?id=CVE-2026-33055 Référence CVE CVE-2026-33056 https://www.cve.org/CVERecord?id=CVE-2026-33056 Référence CVE CVE-2026-33186 https://www.cve.org/CVERecord?id=CVE-2026-33186 Référence CVE CVE-2026-33228 https://www.cve.org/CVERecord?id=CVE-2026-33228 Référence CVE CVE-2026-33810 https://www.cve.org/CVERecord?id=CVE-2026-33810 Référence CVE CVE-2026-33870 https://www.cve.org/CVERecord?id=CVE-2026-33870 Référence CVE CVE-2026-33871 https://www.cve.org/CVERecord?id=CVE-2026-33871 Référence CVE CVE-2026-34073 https://www.cve.org/CVERecord?id=CVE-2026-34073 Référence CVE CVE-2026-34477 https://www.cve.org/CVERecord?id=CVE-2026-34477 Référence CVE CVE-2026-34478 https://www.cve.org/CVERecord?id=CVE-2026-34478 Référence CVE CVE-2026-34480 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0581Multiples vulnérabilités dans MongoDB

De multiples vulnérabilités ont été découvertes dans MongoDB. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance et un problème de sécurité non spécifié par l'éditeur.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0556Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2026-32282 Référence CVE CVE-2026-32283 https://www.cve.org/CVERecord?id=CVE-2026-32283 Référence CVE CVE-2026-32286 https://www.cve.org/CVERecord?id=CVE-2026-32286 Référence CVE CVE-2026-32288 https://www.cve.org/CVERecord?id=CVE-2026-32288 Référence CVE CVE-2026-32289 https://www.cve.org/CVERecord?id=CVE-2026-32289 Référence CVE CVE-2026-32874 https://www.cve.org/CVERecord?id=CVE-2026-32874 Référence CVE CVE-2026-32875 https://www.cve.org/CVERecord?id=CVE-2026-32875 Référence CVE CVE-2026-3298 https://www.cve.org/CVERecord?id=CVE-2026-3298 Référence CVE CVE-2026-32990 https://www.cve.org/CVERecord?id=CVE-2026-32990 Référence CVE CVE-2026-33186 https://www.cve.org/CVERecord?id=CVE-2026-33186 Référence CVE CVE-2026-33230 https://www.cve.org/CVERecord?id=CVE-2026-33230 Référence CVE CVE-2026-33231 https://www.cve.org/CVERecord?id=CVE-2026-33231 Référence CVE CVE-2026-33236 https://www.cve.org/CVERecord?id=CVE-2026-33236 Référence CVE CVE-2026-33810 https://www.cve.org/CVERecord?id=CVE-2026-33810 Référence CVE CVE-2026-33816 https://www.cve.org/CVERecord?id=CVE-2026-33816 Référence CVE CVE-2026-33870 https://www.cve.org/CVERecord?id=CVE-2026-33870 Référence CVE CVE-2026-33871 https://www.cve.org/CVERecord?id=CVE-2026-33871 Référence CVE CVE-2026-34073 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0523Multiples vulnérabilités dans les produits IBM

ecord?id=CVE-2026-22735 Référence CVE CVE-2026-22737 https://www.cve.org/CVERecord?id=CVE-2026-22737 Référence CVE CVE-2026-2391 https://www.cve.org/CVERecord?id=CVE-2026-2391 Référence CVE CVE-2026-24051 https://www.cve.org/CVERecord?id=CVE-2026-24051 Référence CVE CVE-2026-26278 https://www.cve.org/CVERecord?id=CVE-2026-26278 Référence CVE CVE-2026-27601 https://www.cve.org/CVERecord?id=CVE-2026-27601 Référence CVE CVE-2026-27970 https://www.cve.org/CVERecord?id=CVE-2026-27970 Référence CVE CVE-2026-2950 https://www.cve.org/CVERecord?id=CVE-2026-2950 Référence CVE CVE-2026-32141 https://www.cve.org/CVERecord?id=CVE-2026-32141 Référence CVE CVE-2026-33186 https://www.cve.org/CVERecord?id=CVE-2026-33186 Référence CVE CVE-2026-33228 https://www.cve.org/CVERecord?id=CVE-2026-33228 Référence CVE CVE-2026-33532 https://www.cve.org/CVERecord?id=CVE-2026-33532 Référence CVE CVE-2026-3621 https://www.cve.org/CVERecord?id=CVE-2026-3621 Référence CVE CVE-2026-4800 https://www.cve.org/CVERecord?id=CVE-2026-4800 Gestion détaillée du document le 30 avril 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Dé

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0366Multiples vulnérabilités dans Traefik

De multiples vulnérabilités ont été découvertes dans Traefik. Elles permettent à un attaquant de provoquer un contournement de la politique de sécurité.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-010626gRPCにおける認可に関する脆弱性

gRPC-GoはgRPCのGo言語による実装です。バージョン1.79.3より前のものには、HTTP/2の`:path`擬似ヘッダーの不適切な入力検証に起因する認可回避の脆弱性が存在します。gRPC-Goサーバーでは、ルーティングロジックが寛容すぎたため、必須の先頭スラッシュが省略された`:path`（例: `/Service/Method`ではなく`Service/Method`）を含むリクエストを受け入れていました。サーバーはこれらのリクエストを正しいハンドラーにルーティングしましたが、認可インターセプター（公式の`grpc/authz`パッケージを含む）は正規化されていない生のパス文字列を評価していました。その結果、先頭がスラッシュ(`/`)で始まる正規パスを使用する「拒否」ルールがマッチせず、フォールバックの「許可」ルールが存在する場合はポリシーを回避してしまいました。これは、`google.golang.org/grpc/authz`の公式RBAC実装や、`info.FullMethod`または`grpc.Method(ctx)`に依存するカスタムインターセプターなど、パスベースの認可インターセプターを使用し、かつ正規パスに対する特定の「拒否」ルールを含み、他の要求をフォールバックで許可するセキュリティポリシーを持つgRPC-Goサーバーに影響を与えます。この脆弱性は、攻撃者が生のHTTP/2フレームで不正な`:path`ヘッダーを直接gRPCサーバーに送信することで悪用できます。バージョン1.79.3の修正では、先頭スラッシュで始まらない`:path`を持つリクエストは即座に`codes.Unimplemented`エラーで拒否し、認可インターセプターやハンドラーに正規化されていないパス文字列が到達するのを防いでいます。アップグレードが最も安全かつ推奨される対策ですが、次の方法でも緩和可能です。検証用インターセプターの使用（推奨される緩和策）、インフラレベルでの正規化、及びポリシーの強化です。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0306Kwetsbaarheden verholpen in Oracle Fusion Middleware

An authorization bypass vulnerability (CVE-2026-33186) in gRPC-Go prior to version 1.79.3, caused by improper validation of the HTTP/2 :path pseudo-header missing a leading slash, affects multiple products and leads to unauthorized access risks.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
grpc-go: < 1.79.3
Fixed
RHSA-2026:41019: RHEM 1.1 for RHEL 10, RHEM 1.1 for RHEL 9
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
04

Evidence and provenance

Published 20 Mar 2026 · Last source change 18 Sept 2026, 12:04 UTC · CWE-285 · Improper Authorization

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-13830
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:59833.
    Before
    mitigation: github.com/GHSA-p77j-4mvh-x3m3 · remediation: github.com/GHSA-p77j-4mvh-x3m3 · vendor advisory: access.redhat.com/RHSA-2026:59833
    After
    mitigation: github.com/GHSA-p77j-4mvh-x3m3 · remediation: github.com/GHSA-p77j-4mvh-x3m3
    security-advisories@github.com ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:59833.
    Before
    mitigation: github.com/GHSA-p77j-4mvh-x3m3 · remediation: github.com/GHSA-p77j-4mvh-x3m3
    After
    mitigation: github.com/GHSA-p77j-4mvh-x3m3 · remediation: github.com/GHSA-p77j-4mvh-x3m3 · vendor advisory: access.redhat.com/RHSA-2026:59833
    security-advisories@github.com ↗
  3. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:61245.
    Before
    mitigation: github.com/GHSA-p77j-4mvh-x3m3 · remediation: github.com/GHSA-p77j-4mvh-x3m3 · vendor advisory: access.redhat.com/RHSA-2026:61245
    After
    mitigation: github.com/GHSA-p77j-4mvh-x3m3 · remediation: github.com/GHSA-p77j-4mvh-x3m3
    security-advisories@github.com ↗
  4. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:61245.
    Before
    mitigation: github.com/GHSA-p77j-4mvh-x3m3 · remediation: github.com/GHSA-p77j-4mvh-x3m3
    After
    mitigation: github.com/GHSA-p77j-4mvh-x3m3 · remediation: github.com/GHSA-p77j-4mvh-x3m3 · vendor advisory: access.redhat.com/RHSA-2026:61245
    security-advisories@github.com ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 1.79.3 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    grpc-go: < 1.79.3 · Fixed: RHSA-2026:41019: RHEM 1.1 for RHEL 10, RHEM 1.1 for RHEL 9
    CNA ↗
  6. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    security-advisories@github.com ↗
  7. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:56789; removed vendor advisory: access.redhat.com/RHSA-2026:57365.
    Before
    mitigation: github.com/GHSA-p77j-4mvh-x3m3 · remediation: github.com/GHSA-p77j-4mvh-x3m3 · vendor advisory: access.redhat.com/RHSA-2026:56789 · 1 more references
    After
    mitigation: github.com/GHSA-p77j-4mvh-x3m3 · remediation: github.com/GHSA-p77j-4mvh-x3m3
    security-advisories@github.com ↗
  8. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:56789; added vendor advisory: access.redhat.com/RHSA-2026:57365.
    Before
    mitigation: github.com/GHSA-p77j-4mvh-x3m3 · remediation: github.com/GHSA-p77j-4mvh-x3m3
    After
    mitigation: github.com/GHSA-p77j-4mvh-x3m3 · remediation: github.com/GHSA-p77j-4mvh-x3m3 · vendor advisory: access.redhat.com/RHSA-2026:56789 · 1 more references
    security-advisories@github.com ↗
  9. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:56959; removed vendor advisory: access.redhat.com/RHSA-2026:57013.
    Before
    mitigation: github.com/GHSA-p77j-4mvh-x3m3 · remediation: github.com/GHSA-p77j-4mvh-x3m3 · vendor advisory: access.redhat.com/RHSA-2026:56959 · 1 more references
    After
    mitigation: github.com/GHSA-p77j-4mvh-x3m3 · remediation: github.com/GHSA-p77j-4mvh-x3m3
    security-advisories@github.com ↗
  10. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:56959; added vendor advisory: access.redhat.com/RHSA-2026:57013.
    Before
    mitigation: github.com/GHSA-p77j-4mvh-x3m3 · remediation: github.com/GHSA-p77j-4mvh-x3m3
    After
    mitigation: github.com/GHSA-p77j-4mvh-x3m3 · remediation: github.com/GHSA-p77j-4mvh-x3m3 · vendor advisory: access.redhat.com/RHSA-2026:56959 · 1 more references
    security-advisories@github.com ↗
  11. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:56366; removed vendor advisory: access.redhat.com/RHSA-2026:56431.
    Before
    mitigation: github.com/GHSA-p77j-4mvh-x3m3 · remediation: github.com/GHSA-p77j-4mvh-x3m3 · vendor advisory: access.redhat.com/RHSA-2026:56366 · 1 more references
    After
    mitigation: github.com/GHSA-p77j-4mvh-x3m3 · remediation: github.com/GHSA-p77j-4mvh-x3m3
    security-advisories@github.com ↗
  12. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:56366; added vendor advisory: access.redhat.com/RHSA-2026:56431.
    Before
    mitigation: github.com/GHSA-p77j-4mvh-x3m3 · remediation: github.com/GHSA-p77j-4mvh-x3m3
    After
    mitigation: github.com/GHSA-p77j-4mvh-x3m3 · remediation: github.com/GHSA-p77j-4mvh-x3m3 · vendor advisory: access.redhat.com/RHSA-2026:56366 · 1 more references
    security-advisories@github.com ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-13830↗CVE authority or vendor reference · GitHub GHSA-P77J-4MVH-X3M3↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-33186 · cve.blacktree.nl