-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 NEFARIOUSPLAN-CANONICAL-V1 {"body_md":"> The comment named one consumer. The CVE names three more. The grep on trunk this morning names four that the CVE still does not.\n\nThat is the last line of [CVE-2026-24072: AP_EXPR_FLAG_RESTRICTED Was Opt-In For Fifteen Years. The Patch Opts In Three Modules. Four More Still Read /etc/passwd From .htaccess.](/posts/apache-ap-expr-restricted-was-opt-in). The flag has existed since 2011. Two modules in the whole tree ever set it before 2026. The CVE made that number five. The grep on trunk still finds four callers that forgot.\n\nNine case files sit behind this one. All on Apache Software Foundation. All written alone. Stack them and the same sentence writes itself. Apache ships security as a line each author has to remember. The mechanism is there. The invocation is not. The fix, in every file, is the invocation. Copied. Into one more place.\n\n## The fix is always a line somebody else already wrote\n\n[CVE-2026-40858: Same Five Lines. Same Author. Eight Apache Camel Components.](/posts/camel-cve-2026-40858-same-five-lines-eight-components) is the clean case.\n\n> The CVE description names three. The git log names eight.\n\nAndrea Cosentino signed the camel-sql `ObjectInputFilter` on January 9, 2024, and signed the camel-infinispan one on April 14, 2026. Same five lines. Twenty-seven months apart. Six other components got the same patch in between. The deserialization substrate, `DefaultExchangeHolder implements Serializable` plus `ObjectInputStream.readObject()`, has not moved. No module in `camel-support` owns the deserialization step. Each component rolls its own.\n\n[CVE-2026-40453: Camel Patched One Header Filter In 2025. Five More Needed The Same Line.](/posts/camel-cve-2026-40453-five-subclasses-needed-the-same-line) is the same shape in the same vendor, one class higher up the tree.\n\n> `DefaultHeaderFilterStrategy.lowerCase` still defaults to `false` in master. The next subclass that extends it and is used to filter inbound headers will inherit the same one-line patch waiting to be remembered.\n\nOne line, `setLowerCase(true);`, added to `HttpHeaderFilterStrategy` in March 2025 to close CVE-2025-27636. Thirteen months later, the same author lands the same line in five more subclasses to close CVE-2026-40453. The base class default has not changed. The next subclass inherits the hazard, not the fix.\n\nThe ap_expr file is the oldest substrate of the nine.\n\n> The fix is not a new mechanism. The mechanism has existed for fifteen years. The fix is three lines that say *please use it*, in three of the modules that never did.\n\nThree different Apache products. Three different files. Same sentence.\n\n## Opt-in defaults are the plan\n\nThe NiFi file is the one that puts the plan in writing. [CVE-2026-39816: Apache NiFi Patched One Annotation. Ten Days Later, Apache Removed the Mechanism.](/posts/nifi-cve-2026-39816-fix-deprecates-the-mechanism) describes a class annotation every code-executing component author was supposed to remember to write at the top of their class.\n\n> EXECUTE_CODE is whichever components have written `@Restricted(requiredPermission = RequiredPermission.EXECUTE_CODE)` at the top of the class. Forget the tag and the framework has nothing else to consult.\n\nSixteen canonical components wrote it. Three code-executing classes in the graph bundle did not. The CVE is the gap. Ten days after the patch, Apache merged NIFI-15847 and deleted the annotation from sixty-one classes. The NiFi Improvement Proposal that governs the deletion is titled \"Removal of Restricted Component Authorization.\" The release that carries the fix for CVE-2026-39816 is the last release in which the mechanism the fix uses will exist. That is not me interpreting. That is the NIP's own title.\n\nThe file then says the sentence the other eight files are repeating in different words.\n\n> Authorization based on a class-level annotation that every component author has to remember to write is an opt-in security boundary, and one missed opt-in is one CVE.\n\nActiveMQ repeats it with a `Set.of(...)` literal. Camel repeats it with `setLowerCase(true)`. HTTP Server repeats it with a parse flag that is zero by default. mod_http2 repeats it with an assertion the producer side of the same file is not enforcing.\n\n## Two halves of the same concept, written separately, and nobody read both\n\n[CVE-2026-25604: The PoC Tests /login. The Bug Is on /login_callback.](/posts/airflow-aws-saml-poc-tests-wrong-endpoint) is the same disease at the level of one file.\n\n> Two fields. Same call. Same concept, what is this server's hostname? One hardcoded to configuration. One derived from whatever the client sent.\n\n`_init_saml_auth` builds the SAML ACS URL from `conf.get(\"api\", \"base_url\")`. `_prepare_request` builds `http_host` from the inbound `Host` header. Both get passed to `OneLogin_Saml2_Auth(request_data, merged_settings)` in the same call. Same concept, two sources, one contradiction, no reviewer caught it for a year. The fix is four lines. The failure mode is reading one function and not the next.\n\n[CVE-2026-23918: m->spurge Was an h2_ihash. The Array That Replaced It Kept the Assertion, Not the Dedup.](/posts/apache-h2-spurge-was-an-ihash) is the same shape in mod_http2 over fifty-two months.\n\n> The producer changed from \"container guarantees uniqueness\" to \"caller is trusted to not double-add.\" The consumer, which had previously relied on the same container guarantee, was rewritten to scan the array for a duplicate and abort if it found one. Producer enforcement was deleted. Consumer enforcement was preserved as a panic.\n\nAn `h2_ihash` was swapped for an `apr_array`. The consumer-side assertion `ap_assert(\"stream should not be in spurge\" == NULL)` kept the invariant's name. The producer-side guarantee, which was the hash table's deduplication, was deleted. For fifty-two months three producers pushed onto that array without checking, and the consumer aborted the process when it noticed.\n\nThe assertion was telling the truth. The truth was that nobody was enforcing the invariant anymore. Nobody read both halves of the same file.\n\n## The branch is also an author\n\n[CVE-2026-42779: Apache MINA Shipped the Fix on One Branch. The Same Day, Two Other Branches Shipped the Bug.](/posts/mina-fix-shipped-on-one-branch) is where the opt-in sits on the release engineer.\n\n> The fix was in the codebase on 2026-04-24. Two branches shipped that day without it. The window was five days, and the commit message labeled the fix a backport of itself.\n\nOn 2026-04-23, the maintainer committed the fix to 2.0.X with the message \"Added patch regarding whitelist bypassing backported from mina-2.2.X.\" There was no 2.2.X commit. He was labeling his own fix a backport of a commit that did not exist. On 2026-04-24, three releases shipped. One carried the patch. Two did not. The fix landed on 2.1.X and 2.2.X five days later with the commit message \"Added a missing fix.\"\n\nThree live branches. Three release cuts. Each branch is a person who had to remember. One of them did.\n\n## The deny list is the admission\n\n[CVE-2026-34197: ActiveMQ's 5.19.4 Patch Denied One Scheme. Six Weeks Later, the Same Line Denies Fourteen.](/posts/activemq-jmx-denied-schemes-was-one) and [CVE-2026-40466: HTTP Discovery Was Row Two Of A Fourteen-Row Deny List](/posts/activemq-cve-2026-40466-row-two) are the plan written as a `Set` literal.\n\n> The CVE record names one scheme. The deny list ends in `masterslave` until the next commit decides it does not.\n\n5.19.4 banned the `vm` scheme. Six weeks later the same file bans fourteen. One of those fourteen got a CVE because a researcher wrote a Jolokia POST and reported it. The other twelve got patches with PR titles ending in \"part 2.\" The maintainer knew. The codebase was being read in waves by its own author. Only the rows scanners noticed got numbers.\n\n> The deny list has fourteen entries. Two have CVEs.\n\nA deny list is an opt-in security boundary with a keyboard instead of an annotation. Each row is a name the author had to remember. The parameter type is still `String`. The URI registry is still open. The signature of `addNetworkConnector(String)` has not changed since 4.x.\n\n## Where you are right\n\nThe engine is not the charge. Java's `ObjectInputStream.readObject()` is a known hazard the language ships with. `AP_EXPR_FLAG_RESTRICTED` is a correct mechanism and does what the comment above it says. The `@Restricted` annotation enforces what the NiFi authorization layer reads out of it. `_init_saml_auth` in Airflow hardcodes the ACS URL correctly; the PoC's mock is a stronger version of the bug than the real code. Stefan Eissing's assertion in `h2_mplx.c` was named with the right words; the invariant it checks is real. Christopher Shannon's `validateAllowedScheme` is correct code; it does what its body says.\n\nNone of the controls in these files are broken. Every one of them does its job.\n\nThe charge is the shape of the ship. Apache keeps publishing correct mechanisms as idioms every author has to invoke. The call site is the gate. The gate is in every author's head.\n\n## Where the next one comes from\n\nOpen `BrokerView.java` on `activemq-5.19.x`. Read the `DENIED_TRANSPORT_SCHEMES` literal. The transport factories registered under `META-INF/services/org/apache/activemq/transport/` that are not on that list are the next rows. A PR title ending in \"part 3\" is the signal.\n\nOpen `include/ap_expr.h` on httpd trunk. Read `AP_EXPR_FLAG_RESTRICTED`. Grep for `ap_expr_parse_cmd(`. Read the override class on every containing directive. Any directive declared `OR_FILEINFO` or `OR_OPTIONS` whose parse site does not pass the flag is a candidate. The ap_expr file names four of them: `mod_headers`, `mod_alias`, `mod_substitute`, `mod_filter`.\n\nOpen `camel-support`. Search for a shared deserialization codec. There is not one. Each Camel component's `readObject()` is its own site. The ninth is whichever component adds remote persistence next.\n\nOpen NIP-24. NiFi 2.10.0 removes `@Restricted` entirely and shifts the gate to the standard component-edit policy. Audit which NARs an operator can load and who has component-create rights, because that is the only gate 2.10.0 will have.\n\nNone of this is an exploit. It is the directory listing of what the vendor has written down and left opt-in.\n\n## What the next advisory will say\n\nThe next Apache advisory will do one of three things.\n\nA row will be added to `DENIED_TRANSPORT_SCHEMES` in `BrokerView.java` on `activemq-5.19.x`, with a PR title naming a transport scheme already present in `META-INF/services/org/apache/activemq/transport/`.\n\nOr `AP_EXPR_FLAG_RESTRICTED` will be added to one of `mod_headers.c`, `mod_alias.c`, `mod_substitute.c`, or `mod_filter.c`, in a commit whose diff is three lines with a `cmd->pool == cmd->temp_pool` check already written by r1933350.\n\nOr a ninth Camel component will get its own copy of `ObjectInputFilter.Config.getSerialFilter()` in a commit signed by Andrea Cosentino.\n\nThe prediction is called when any one of those three lands. The prediction is missed if the next Apache advisory does none of them.","closing_line":"To Apache. The plan is in your commit log. You wrote \"part 2\" in a commit title, labeled a fix the backport of itself, and left \"e.g.\" standing for fifteen years, and the fix for the next one is the invocation you already wrote, copied into one more file.","hook_md":"These are nine Apache case files, each about one bug. Stacked together, they write the same sentence. The vendor keeps shipping security as a line every author has to remember, and every fix is the same invocation, copied into one more file.","post_id":861,"slug":"the-nefarious-plan-of-apache-software-foundation","title":"The Nefarious Plan of Apache Software Foundation","type":"editorial","unreadable_sentence":"Apache ships security as a line each author has to remember."} -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQRf0htP5+SjynlxywneZjl4jgkQJgUCavqJbAAKCRDeZjl4jgkQ Jn32AQDplKWaZdKyhWNrkJTUUAWVxKNdZOySx4FAS4IbbS1hWQD/SThvipNvXzqn m4TuXbx+AC6laJc4UpQVWp9cCXTpRwQ= =Ut3D -----END PGP SIGNATURE-----