Action required: nginx HTTP/2 vulnerabilities (CVE-2026-123007, CVE-2026-123633)
On November 18, 2026, two vulnerabilities in the HTTP/2 handling of nginx were disclosed (CVE-2026-123007 and CVE-2026-123633). A crafted HTTP/2 request may allow arbitrary code to be executed without authentication.
The Marketplace edition of AGENTIC STAR uses ingress-nginx as its entry point in v3.3.x and earlier. ingress-nginx is no longer developed by the community, and no fixed version will be provided. Please disable HTTP/2 at the entry point of your environment by following the steps below.
Scope
| Product | Action on your side |
|---|---|
| Marketplace edition (Agenticstar ADK Advanced and Basic). v3.3.x and earlier, all clouds | Required (follow these steps) |
| Marketplace edition v3.4.0 and later | Not required (see "v3.4.0" below) |
| SaaS edition | Not required (we handle it) |
Even if you restrict the source IP addresses allowed to reach the entry point, the allowed sources can still reach it over HTTP/2. Please take this action regardless of such restrictions.
v3.4.0
From v3.4.0, the entry point is NGINX Gateway Fabric. NGINX Gateway Fabric in v3.4.0 runs on an nginx version that fixes these vulnerabilities.
| Environment | Action on your side |
|---|---|
| Newly deployed with v3.4.0 | Not required (ingress-nginx is not installed) |
| Updated from v3.3.x or earlier to v3.4.0 on the Version Management page (Method A) | During the update, the entry point switches to NGINX Gateway Fabric and ingress-nginx is stopped (see "A-10. Entry switch when updating to v3.4.0" in the Version Upgrade Guide). After the switch, no action is required. Until you update to v3.4.0, disable HTTP/2 by following these steps |
| The entry switch failed during the update to v3.4.0 | The entry point is still ingress-nginx. Until the switch is retried, check with step 3 that HTTP/2 is disabled, and run step 2 if it is not |
Steps
This takes about 5 minutes. No Pods are restarted, and you do not need to stop using the service.
1. Connect to the cluster
Connect kubectl to the cluster in the same way as during deployment.
- Azure: "Verifying the Deployment" in the quickstart
- AWS: "Configure kubectl" under "After Deployment" in the quickstart
2. Disable HTTP/2
kubectl patch configmap ingress-nginx-controller -n ingress-nginx \
--type merge -p '{"data":{"use-http2":"false"}}'
The entry point reloads its configuration within a few seconds. Existing connections switch to the new configuration within about 4 minutes at most.
3. Verify
kubectl exec -n ingress-nginx deploy/ingress-nginx-controller -- \
sh -c 'nginx -T 2>/dev/null | grep -c "http2 on" || true'
If 0 is shown, HTTP/2 is disabled (before the change, the value is 1 or more).
You can also verify from your own machine. Replace <address> with the host name or IP address you use to open AGENTIC STAR.
curl -sk -o /dev/null -w '%{http_version}\n' --http2 https://<address>/
If 1.1 is shown, HTTP/2 is disabled (before the change, 2 is shown).
Impact
- Communication between browsers and the entry point uses HTTP/1.1. The features of the screens and the API do not change.
- With HTTP/1.1, browsers limit the number of simultaneous connections to one destination (6 in major browsers). If you open AGENTIC STAR in many tabs of the same browser, pages may wait to load. In that case, close the tabs you are not using.
- If you upgrade the product while staying on v3.3.x or earlier, verify again with step 3. If HTTP/2 is not disabled, run step 2 again.
Revert
kubectl patch configmap ingress-nginx-controller -n ingress-nginx \
--type json -p '[{"op":"remove","path":"/data/use-http2"}]'