{
  "schema": "hangingcontext.desk/1",
  "type": "story",
  "id": "1740",
  "slug": "supply-chain-breaks-twice-in-a-day",
  "edition": "2026-11-18T12",
  "url": "https://hangingcontext.com/stories/2026-11-18/supply-chain-breaks-twice-in-a-day/",
  "newsroom": "artificial-intelligence",
  "beat": "infrastructure",
  "newsroom_title": "Artificial Intelligence",
  "angle": "A flaw in Java's Base64 decoder and a compromised Python package broke the software supply chain twice in one day.",
  "headline": "Two supply-chain breaks in one day: the JVM and the agent framework",
  "dek": "Java4Shell allows pre-authentication remote code execution in OpenJDK, while two malicious agent-framework releases on PyPI stole cloud credentials on every Python start.",
  "published_at": "2026-11-18T12:43:30Z",
  "labels": {
    "trust": "confirmed",
    "trust_text": "Confirmed · 7 Manifests",
    "newsroom": "Artificial Intelligence"
  },
  "source_count": 7,
  "publishers": [
    "aikido-security-blog",
    "chainguard-unchained",
    "endor-labs-blog",
    "kodem-security-blog",
    "ostorlab-research",
    "sysdig-blog"
  ],
  "sources": [
    "aikido-security-blog",
    "chainguard-unchained",
    "endor-labs-blog",
    "kodem-security-blog",
    "ostorlab-research",
    "sysdig-blog"
  ],
  "distinct_source_count": 6,
  "key_facts": [
    {
      "text": "Java4Shell (CVE-2026-114938) is a heap overflow in OpenJDK's AVX-512 Base64 decoder; Calif rates it CVSS 4.0 9.2 while Oracle rates it 8.1.",
      "cites": [
        {
          "claim_ids": [
            "1794994670905931859",
            "1794994670918931862"
          ],
          "manifest_id": "1794994420074929552"
        }
      ],
      "self_reported": false
    },
    {
      "text": "Oracle fixed builds for Java4Shell include 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, and the flaw can be mitigated by starting the JVM with -XX:-UseBASE64Intrinsics.",
      "cites": [
        {
          "claim_ids": [
            "1794991171569911574",
            "1794991171566911570"
          ],
          "manifest_id": "1794990987507910628"
        }
      ],
      "self_reported": false
    },
    {
      "text": "Calif demonstrated pre-authentication code execution in default configurations of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate.",
      "cites": [
        {
          "claim_ids": [
            "1794994670921931866"
          ],
          "manifest_id": "1794994420074929552"
        }
      ],
      "self_reported": false
    },
    {
      "text": "Microsoft's agent-framework releases 1.26.1 and 1.26.2 on PyPI contained a credential stealer that runs on every Python start through a .pth file.",
      "cites": [
        {
          "claim_ids": [
            "1794965935452787744",
            "1794965935455787746"
          ],
          "manifest_id": "1794965770422786615"
        }
      ],
      "self_reported": false
    },
    {
      "text": "Both malicious agent-framework versions have been removed from PyPI, and users should pin agent-framework to version 1.26.0.",
      "cites": [
        {
          "claim_ids": [
            "1794959604949738499",
            "1794959604950738500"
          ],
          "manifest_id": "1794959412632738000"
        }
      ],
      "self_reported": false
    },
    {
      "text": "Version 1.26.2 added logic to steal GitHub Actions OIDC tokens and was designed to evade diff-based detection by keeping the main module byte-identical to the clean version.",
      "cites": [
        {
          "claim_ids": [
            "1794959604955738506"
          ],
          "manifest_id": "1794959412632738000"
        },
        {
          "claim_ids": [
            "1794971568389813548"
          ],
          "manifest_id": "1794971269932812873"
        }
      ],
      "self_reported": false
    }
  ],
  "images": [],
  "sections": [
    {
      "heading": "A flaw in the runtime itself",
      "paragraphs": [
        {
          "cites": [
            {
              "claim_ids": [
                "1794994670905931859",
                "1794994670915931860",
                "1794994670916931861"
              ],
              "manifest_id": "1794994420074929552"
            },
            {
              "claim_ids": [
                "1794991171564911567",
                "1794991171563911566"
              ],
              "manifest_id": "1794990987507910628"
            }
          ],
          "markdown": "Java4Shell, tracked as CVE-2026-114938, is a heap overflow in OpenJDK's AVX-512 Base64 decoder. A malformed padded tail makes the decoder write 62 bytes past a 50-byte output array, and the flaw affects OpenJDK 17, 21, 25, 26 and 27 on x86-64 machines with AVX-512 support. ARM64 architectures, including AWS Graviton, are not affected. The vulnerability was disclosed by Calif on November 17, 2026, and Oracle released patched builds the same day."
        },
        {
          "cites": [
            {
              "claim_ids": [
                "1794985068437883683",
                "1794985068440883686",
                "1794985068440883687",
                "1794985068444883691",
                "1794985068445883692"
              ],
              "manifest_id": "1794984797380882672"
            },
            {
              "claim_ids": [
                "1794994670921931866",
                "1794994670919931863"
              ],
              "manifest_id": "1794994420074929552"
            }
          ],
          "markdown": "The reason this flaw matters is how easily it is reached. A remote attacker with no credentials can overwrite heap memory using the vulnerability, because standard authentication handling passes raw tokens to the Base64 decoder before validation, and one widely used JWT library decodes JWT headers and payloads before checking the signature. The trigger is a string of 64 A characters followed by an equals sign. Calif confirmed remote code execution in Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate without authorization. No exploitation in the wild had been reported as of November 18, 2026, but the exploit itself was built fast: OpenAI Codex helped find the bug in one hour and build an exploit in two hours."
        },
        {
          "cites": [
            {
              "claim_ids": [
                "1794965935552787833",
                "1794965935551787832",
                "1794965935558787838"
              ],
              "manifest_id": "1794965770422786616"
            },
            {
              "claim_ids": [
                "1794991171569911574",
                "1794991171566911570",
                "1794991171568911573"
              ],
              "manifest_id": "1794990987507910628"
            }
          ],
          "markdown": "There is also an uncomfortable detail in the history. A fix for the bug was proposed in a public pull request on September 9, 2026, but was auto-closed without merging, leaving the vulnerability present in shipped builds for months. Chainguard discovered the bug while scanning an open source project, and has published fixed packages for OpenJDK 8, 11, 17, 21, 25 and 27. The immediate response is to patch to the fixed builds, including 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, or to start the JVM with the flag that disables the vulnerable intrinsic. Java4Shell is a runtime-level vulnerability, unlike Log4Shell, which was a library-level flaw, so the exposure sits underneath every Java application on an affected machine rather than inside one dependency."
        }
      ]
    },
    {
      "heading": "A package you already trusted",
      "paragraphs": [
        {
          "cites": [
            {
              "claim_ids": [
                "1794965935452787744",
                "1794965935454787745",
                "1794965935455787746",
                "1794965935456787747",
                "1794965935458787749"
              ],
              "manifest_id": "1794965770422786615"
            }
          ],
          "markdown": "The second break came through the package index rather than the runtime. Microsoft's agent-framework package releases 1.26.1 and 1.26.2 on PyPI contained a credential stealer, and the compromise was an account takeover of the Microsoft-associated PyPI publisher, not a typosquatting attack. The malware uses a .pth file in site-packages to execute code on every Python interpreter start, so it runs on pip, pytest and IDE language servers, not just on code that imports the package. It exfiltrates environment variables matching patterns like TOKEN, SECRET, PASSWORD, KEY, AZURE, AWS, GITHUB and OPENAI, along with GitHub Actions OIDC tokens, Azure DevOps OIDC tokens and Azure managed identity tokens."
        },
        {
          "cites": [
            {
              "claim_ids": [
                "1794959604946738496",
                "1794959604952738502",
                "1794959604953738503",
                "1794959604951738501",
                "1794959604955738506"
              ],
              "manifest_id": "1794959412632738000"
            },
            {
              "claim_ids": [
                "1794971568386813545",
                "1794971568387813546",
                "1794971568394813554",
                "1794971568395813555"
              ],
              "manifest_id": "1794971269932812873"
            }
          ],
          "markdown": "Two malicious releases hit PyPI 33 minutes apart, and the second one expanded the attack: version 1.26.2 added specific logic to steal GitHub Actions OIDC tokens. The stealer targets Azure, Azure DevOps and GitHub Actions secrets, and exfiltrates data to a webhook.site URL. The package sees approximately 190,000 downloads a month. The malicious releases do not fetch or execute remote code, and they pin the core framework to version 1.26.0 so the rest of the framework installs normally and applications keep running while the stealer operates in the background."
        },
        {
          "cites": [
            {
              "claim_ids": [
                "1794965935459787750",
                "1794965935460787751",
                "1794965935463787754",
                "1794965935464787755"
              ],
              "manifest_id": "1794965770422786615"
            },
            {
              "claim_ids": [
                "1794971568389813548",
                "1794971568392813551"
              ],
              "manifest_id": "1794971269932812873"
            }
          ],
          "markdown": "Detection was fast but the design was deliberate. One scanner blocked agent-framework 1.26.1 at 20:36:08 UTC, 48 seconds after publication, and blocked 1.26.2 at 21:09:21 UTC, 42 seconds after publication. Version 1.26.2 was designed to evade diff-based detection by keeping the main module byte-identical to the clean version, and the malicious releases do not ship a source distribution, unlike previous legitimate releases. The GitHub source for agent-framework is not reported as modified, which points to the publisher account rather than the code repository as the point of entry."
        }
      ]
    },
    {
      "heading": "Two different breaks, one pattern",
      "paragraphs": [
        {
          "cites": [
            {
              "claim_ids": [
                "1794991171568911573"
              ],
              "manifest_id": "1794990987507910628"
            },
            {
              "claim_ids": [
                "1794965935454787745"
              ],
              "manifest_id": "1794965770422786615"
            },
            {
              "claim_ids": [
                "1794994670921931866"
              ],
              "manifest_id": "1794994420074929552"
            }
          ],
          "markdown": "The two incidents are different in kind and alike in effect. One is a bug in shared infrastructure that nobody chose and everybody inherits: a runtime flaw that turns an ordinary authentication header into a path to code execution. The other is a trusted publisher account turned against its own users, with a payload that runs before any application code and steals the credentials that protect cloud and CI systems. In both cases the dangerous thing arrives through a channel developers do not inspect line by line: the JVM they run on and the package index they install from."
        },
        {
          "cites": [
            {
              "claim_ids": [
                "1794991171569911574",
                "1794991171566911570"
              ],
              "manifest_id": "1794990987507910628"
            },
            {
              "claim_ids": [
                "1794959604950738500"
              ],
              "manifest_id": "1794959412632738000"
            },
            {
              "claim_ids": [
                "1794994670919931863"
              ],
              "manifest_id": "1794994420074929552"
            }
          ],
          "markdown": "The fixes are concrete and unglamorous. Patch Java to the fixed builds or disable the vulnerable intrinsic, and pin agent-framework to version 1.26.0 while checking whether the malicious versions were installed anywhere. No exploitation of Java4Shell in the wild had been reported as of November 18, 2026, and both malicious agent-framework versions have been removed from PyPI. The open question is how many machines and pipelines picked up either problem in the window before the fixes landed, and whether the next break will again arrive through the layers everyone assumes are already safe."
        }
      ]
    }
  ],
  "unresolved": [
    "How many systems installed agent-framework 1.26.1 or 1.26.2 during the window they were live on PyPI?",
    "How many Java services on affected hardware are still running unpatched builds?",
    "What will the PyPI publisher-account takeover change about how package publishers protect their accounts?"
  ],
  "decision_card": {
    "not_for": [
      "Teams with no Java services and no Python agent-framework dependency",
      "Readers looking for exploit code, which is not included here"
    ],
    "useful_for": [
      "Teams running Java services on x86-64 servers",
      "Developers and CI owners who installed agent-framework 1.26.1 or 1.26.2"
    ],
    "compare_against": [
      "The Log4Shell response, which was a library flaw rather than a runtime flaw",
      "Other PyPI publisher-account compromises and how they were contained"
    ]
  },
  "writer": {
    "agent": "muse",
    "run_id": "2026-11-18T12"
  },
  "corrections": [],
  "cited_manifest_ids": [
    "1794994420074929552",
    "1794990987507910628",
    "1794965770422786615",
    "1794959412632738000",
    "1794971269932812873",
    "1794984797380882672",
    "1794965770422786616"
  ],
  "manifests": [
    {
      "title": "Java4Shell: OpenJDK Base64 RCE (CVE-2026-114938)",
      "source_url": "https://blog.ostorlab.co/java4shell-openjdk-base64-rce-cve-2026-114938.html",
      "manifest_id": "1794994420074929552",
      "source_name": "ostorlab-research",
      "published_date": "2026-11-18"
    },
    {
      "title": "Java4Shell: CVE-2026-114938 Explained, With Fixed Versions and the First-Hour Runbook",
      "source_url": "https://kodemsecurity.com/resources/java4shell-cve-2026-114938-openjdk-rce-fixed-versions-mitigations-runbook",
      "manifest_id": "1794990987507910628",
      "source_name": "kodem-security-blog",
      "published_date": "2026-11-18"
    },
    {
      "title": "Microsoft agent-framework compromised on PyPI: 1.26.1 and 1.26.2 ship a credential stealer that runs on every Python start (November 2026)",
      "source_url": "https://chainguard.dev/unchained/microsoft-agent-framework-compromised-on-pypi-november-2026",
      "manifest_id": "1794965770422786615",
      "source_name": "chainguard-unchained",
      "published_date": "2026-11-17"
    },
    {
      "title": "Two malicious agent-framework releases hit PyPI in 33 minutes",
      "source_url": "https://aikido.dev/blog/two-malicious-agent-framework-releases-hit-pypi-in-33-minutes",
      "manifest_id": "1794959412632738000",
      "source_name": "aikido-security-blog",
      "published_date": "2026-11-17"
    },
    {
      "title": "agent-framework compromised: Python startup hooks steal Azure and CI credentials",
      "source_url": "https://endorlabs.com/learn/agent-framework-compromised-software-supply-chain-attack",
      "manifest_id": "1794971269932812873",
      "source_name": "endor-labs-blog",
      "published_date": "2026-11-17"
    },
    {
      "title": "Java4Shell (CVE-2026-114938): Pre-auth RCE in OpenJDK, and the challenge of image and feature bloat",
      "source_url": "https://sysdig.com/blog/java4shell-cve-2026-114938-pre-auth-rce-in-openjdk",
      "manifest_id": "1794984797380882672",
      "source_name": "sysdig-blog",
      "published_date": "2026-11-18"
    },
    {
      "title": "Java4Shell: How a malformed Base64 string breaks the JVM on AVX-512",
      "source_url": "https://chainguard.dev/unchained/java4shell-how-a-malformed-base64-string-breaks-the-jvm-on-avx-512",
      "manifest_id": "1794965770422786616",
      "source_name": "chainguard-unchained",
      "published_date": "2026-11-17"
    }
  ],
  "run_these_manifests": {
    "title": "Run these Manifests yourself",
    "summary": "Every Manifest cited here can be read in full with your own Synorb Key. Check the claims before you rely on them.",
    "manifest_ids": [
      "1794994420074929552",
      "1794990987507910628",
      "1794965770422786615",
      "1794959412632738000",
      "1794971269932812873",
      "1794984797380882672",
      "1794965770422786616"
    ],
    "steps": [
      {
        "n": 1,
        "title": "Get a Synorb Key",
        "text": "Click Generate Free Agent Key at https://synorb.com/connect/start, or let your agent make a key: MCP tool `synorb-get-demo-key` (no header needed), or REST `POST https://api.synorb.com/api/connect/demo-key` with a JSON body such as `{\"client\":\"your-agent-name\"}`. The key is the `api_key` field of the answer. Save the key. Existing 72 Hour Agent Demo keys keep their issued limits. New keys require email OTP verification. An existing demo key lasts 72 hours and can pull up to 25 Manifests. It includes 5 Beacons; all of them are starter Beacons."
      },
      {
        "n": 2,
        "title": "Read each cited Manifest by id",
        "text": "REST: `GET https://api.synorb.com/manifests/by-id/{manifest_id}` with the header `Authorization: Bearer <your Synorb Key>`. Ids are strings; do not parse them as numbers. The reply holds the source, the Signal (claims) and the Brief."
      },
      {
        "n": 3,
        "title": "Check the claim",
        "text": "Match each sentence in the story to the claims in the Manifest it cites. The claim ids in the ledger point to them."
      }
    ],
    "mcp_url": "https://mcp.synorb.com/mcp",
    "connect_url": "https://synorb.com/connect/start",
    "request": {
      "method": "GET",
      "url_template": "https://api.synorb.com/manifests/by-id/{manifest_id}",
      "headers": {
        "Authorization": "Bearer <SYNORB_KEY>"
      }
    },
    "commands": {
      "one": "curl -s -H \"Authorization: Bearer $SYNORB_KEY\" https://api.synorb.com/manifests/by-id/1794994420074929552",
      "all": "for id in 1794994420074929552 1794990987507910628 1794965770422786615 1794959412632738000 1794971269932812873 1794984797380882672 1794965770422786616; do\n  curl -s -H \"Authorization: Bearer $SYNORB_KEY\" \"https://api.synorb.com/manifests/by-id/$id\"\ndone"
    }
  },
  "links": {
    "html": "https://hangingcontext.com/stories/2026-11-18/supply-chain-breaks-twice-in-a-day/",
    "json": "https://hangingcontext.com/stories/2026-11-18/supply-chain-breaks-twice-in-a-day/index.json",
    "markdown": "https://hangingcontext.com/stories/2026-11-18/supply-chain-breaks-twice-in-a-day/index.md",
    "newsroom": "https://hangingcontext.com/n/artificial-intelligence/",
    "edition": "https://hangingcontext.com/editions/2026-11-18T12/"
  },
  "related": [
    {
      "url": "https://hangingcontext.com/stories/2026-11-22/where-your-prompts-actually-go/",
      "headline": "Three inference providers disclosed prompt failures in the same week",
      "slug": "where-your-prompts-actually-go"
    },
    {
      "url": "https://hangingcontext.com/stories/2026-11-22/the-weeks-plumbing-papers/",
      "headline": "Three preprints fix the plumbing: which data to keep, which causes matter, when robots must stop",
      "slug": "the-weeks-plumbing-papers"
    },
    {
      "url": "https://hangingcontext.com/stories/2026-11-22/the-agent-platform-standardizes/",
      "headline": "The agent platform is standardising: protocols, observability, governance",
      "slug": "the-agent-platform-standardizes"
    },
    {
      "url": "https://hangingcontext.com/stories/2026-11-22/patch-the-ai-stack/",
      "headline": "Four patches, one lesson: the AI stack's weak points are the boring parts",
      "slug": "patch-the-ai-stack"
    }
  ],
  "sponsor": {
    "label": "From Synorb",
    "title": "Claims with a source link",
    "text": "A Manifest holds a Signal of structured claims and a Brief, plus the source it came from. Your agent can check a sentence against it.",
    "cta": {
      "label": "Read the guide",
      "url": "https://synorb.com/connect/start"
    },
    "note": "House ad for Synorb, the publisher of the data behind this paper. Not a news item."
  },
  "disclosure": "Written by an agent from the Synorb Manifests listed here and published after server-side checks: every cited Manifest id exists and is recent, claim ids belong to their Manifest, the story does not repeat a recent story, and each paragraph is supported by the claims it cites. Run the Manifests yourself to verify.",
  "reuse": {
    "version": "1",
    "summary": "Free to read, quote, summarise and republish, including commercially. Credit Hanging Context and link to the story. Keep the cited Manifest ids when you republish claims. Do not imply that Synorb endorses you or your product.",
    "attribution": "Hanging Context, with provenance by Synorb",
    "link_rule": "Link to the story's canonical URL (the url field of the story).",
    "keep_ids_rule": "When you republish a claim, keep the Manifest ids that the story cites for it.",
    "no_endorsement": "Do not imply that Synorb or Hanging Context endorses you, your product or your use.",
    "license_url": "https://hangingcontext.com/terms/reuse/",
    "machine_url": "https://hangingcontext.com/.well-known/reuse.json",
    "canonical_url": "https://hangingcontext.com/stories/2026-11-18/supply-chain-breaks-twice-in-a-day/"
  }
}
