Friday, November 20, 2026

Review – Bills Introduced – 11-19-26

Yesterday, with both the House and Senate in session, but preparing to leave for their Thanksgiving work period, there were 104 bills introduced. Two of those bills will receive additional coverage in this blog: 

HR 11119 To direct the Administrator of the Transportation Security Administration to establish a grant program for eligible railroads to assist in financing the cost of improving the cybersecurity of freight rail transportation systems, and for other purposes. Shreve, Jefferson [Rep.-R-IN-6]    

HR 11127 To direct the Director of the National Institute of Standards and Technology to establish benchmarks for the timely remediation of software vulnerabilities by owners and operators of critical infrastructure, to establish a grant program for patch modernization and the reduction of the exposure of operational technology, and for other purposes. Whitesides, George [Rep.-D-CA-27]   


For more information on these bills, including legislative history for similar bills in the 118th Congress, as well as a mention-in-passing of a bill to aid the separation of military members, see my article at CFSN Detailed Analysis - https://patrickcoyle.substack.com/p/bills-introduced-11-19-26 - subscription required. 

Thursday, November 19, 2026

Review – 3 Advisories Published – 11-19-26

Today CISA’s NCCIC-ICS published three control system security advisories for products from libumqtt, Elecbrakes, and Autonomy Logic. 

Advisories  

Libumqtt Advisory - This advisory describes an integer underflow vulnerability in the libumqtt library. The vulnerability was reported to CISA by Joseph Devasia. 

Elecbrakes Advisory - This advisory describes three vulnerabilities in the Elecbrakes EB2, VM1, ELBC2000 electronic break controllers. The vulnerabilities were reported to CISA by Patrick Forck and Jeremy McCarthy of Element Digital. 

Autonomy Advisory - This advisory describes a race condition vulnerability in the Autonomy Logic OpenPLC Runtime. The vulnerability was reported to CISA by Noureddin Lutfi. 


For more information on these advisories, as well as a DTRH look at another reported library vulnerability, see my article at CFSN Detailed Analysis - https://patrickcoyle.substack.com/p/3-advisories-published-11-19-26 - subscription required. 

Review – Bills Introduced – 11-18-26

Yesterday, with both the House and Senate in session, there were 59 bills introduced. Three of those bills may receive additional coverage in this blog: 

HR 11055 To amend the Homeland Security Act of 2002 to establish within the Cybersecurity and Infrastructure Security Agency a pilot program to be known as the "BRIDGE AI Mission Program" to recruit and manage artificial intelligence and emerging technology professionals on a temporary basis to support the core mission of the Agency, and for other purposes. Fong, Vince [Rep.-R-CA-20]    

HR 11069 To amend the Homeland Security Act of 2002 to designate the Department of Homeland Security as the Sector Risk Management Agency for the information technology sector, require the Cybersecurity and Infrastructure Security Agency to carry out the responsibilities of the Department for such sector, strengthen public and private sector engagement to reduce cybersecurity risks to such sector and secure its systems, assets, and key resources against cybersecurity threats, supply chain compromise, and physical threats, including terrorism threats to the United States, and for other purposes. Ogles, Andrew [Rep.-R-TN-5]    

HR 11076 To amend the Homeland Security Act of 2002 to require the Director of the Cybersecurity and Infrastructure Security Agency to lead cybersecurity efforts relating to the secure adoption, discovery, identification, authorization, monitoring, accountability, and risk management of artificial intelligence agents operating on executive agency information systems, and for other purposes. Van Epps, Matt [Rep.-R-TN-7]


For more information on these bills, including legislative history for similar bills in the 118th Congress, as well as a mention-in-passing of a bill to support influenza research, see my article at CFSN Detailed Analysis - https://patrickcoyle.substack.com/p/bills-introduced-11-18-26 - subscription required. 

Short Takes – 11-19-26 - Space Geek Edition

Jamming is a much bigger problem than we think. SpaceNews commentary. Pull quote: “Any enemy will look for vulnerabilities in whatever equipment and processes military forces use, and governments will need to keep testing their defences as technology develops. In every conflict, military technology develops through a constant race between offensive weapons and the means to counter them. The Pentagon knows this, of course, and will be taking steps accordingly. But a wider consciousness of the problem of jamming is needed. A satellite does not have to suffer damage for an adversary to leave those who depend on it unable to communicate when they most need to.” 

Amazon loses 40 Leo satellites in ULA Vulcan launch failure — a new setback for its Starlink rival. GeekWire.com article. Pull quote: “Sunday’s mission was the fifth for Vulcan, which debuted in January 2024, and the first with six solid boosters. Boosters suffered nozzle failures on the second flight in October 2024 and on a national security mission in February. Both reached orbit, but the Space Force paused Vulcan national security launches after February.” 

SpaceNukes Opens Los Alamos Manufacture and Materials Facility to Build Its Next-Generation Space Reactor. SpaceNews.com article. Pull quote: “Additive manufacturing is used only for specific circumstances,” Mireles said. “You have parts that are highly complex, made from materials that are difficult to form, have a low production rate that won’t benefit from economy of scale, and have the design flexibility that can optimize designs to the manufacturing process. These lessons were learned over the last two decades in the liquid rocket engine community, and we are applying them to the needs of SpaceNukes, which have very similar conditions. We are manufacturing aerospace components at aerospace-quality standards. This building is where we learn to make them.” 

What's next for SpaceX's Starship after epic Flight 15 chopsticks catch? Space.com article. Pull quote: “We're likely to see the first refueling test relatively soon, as time is of the essence for SpaceX. If the company can't get Ship ready for the Artemis IV moon landing in 2028, NASA may go with another private lander — Blue Origin's Blue Moon, which the agency also contracted for Artemis missions.” 

Dancing in Orbit: In-Space Mobility. Starbench Analysis article. Pull quote: “The better argument for in-space maneuvering is as a platform. Once this capability comes online, what other applications and startups are enabled by it that didn’t make sense before? Maybe GEO gets opened up to smaller players operating on a budget. Perhaps these same craft can start going out beyond GEO into cislunar space, on cycler orbits, etc. It seems like for medium to large space companies trying to build platforms, having one of these vehicles in the roster will come in handy.” 

Scientists Are Stumped by This Strange Object in Space. NYTimes.com article. Pull quote: ““There’s all sorts of space junk out there,” said Bryce T. Bolin, a scientist at Eureka Scientific Inc., a research corporation, who has written about 1998 KY26. “But this object is way too heavy, way too dense.” Dr. Bolin added that 1998 KY26 had the density of — you’ll never guess — a rock.” 

Sophia Space deploys on-orbit computing software. SpaceNews.com article. Pull quote: “Sophia’s vision for a future on-orbit computing architecture includes both SOOS and its modular Thermal-Integrated LEO Edge, or TILE, technology. The solar-powered, passively-cooled TILEs function as a compute engine that Sophia says is lighter weight and more efficient than what its competitors are offering. The company, in partnership with the California Institute of Technology, received a patent in July for its cooling system, which emits its own heat into space without a need for radiators.” 

Wednesday, November 18, 2026

Peoria Chemplant Bomb

Last week, I mentioned on my social media posts an article on NYTimes.com about a bomb that had been found at a chemical plant in Peoria, IL. It had been neutralized by authorities, and the investigation was ongoing. What with the other goings on that weekend, the story did not get much of a play nationally. Yesterday, it was announced (see here and here) that a plant employee had been charged with making the bomb threat and electronically communicating that threat. No details are (or probably will be) available on the size or sophistication of the device. 

What Could Have Happened  

First off, there is a reason that DHS has focused their bombing prevention activities at chemical plants (see my post here for example) on vehicle-borne improvised-explosive devices (VBIED). Chemical plants are robustly constructed. An unsophisticated bomber is going to need a large explosive device to be sure of a catastrophic effect, and terrorist want the most catastrophic effect that they can get. 

Having said that, using a sophisticated device the size of a grade school backpack, properly placed at a strategic point on a large ethanol storage tank, you could easily cause a large hole in the tank structure that would lead to an uncontrollable discharge of the contents of the tank. Even if you did not get ignition at the point of detonation (not guaranteed no matter what Hollywood says), the fumes released from a large pool of discharged ethanol could very easily find a source of ignition some distance from the tank. The fume-flames would likely get back (flash back) to the pool of ethanol in the containment area, and the resulting pool fire could cause problems at other storage tanks. Foam firefighting techniques are well suited to addressing those types of pool fires. Many larger chemical facilities have in-house teams specifically trained and equipped to fight pool fires. 

A less sophisticated device, or a more poorly placed device, would be unlikely to cause such a large hole to be made in the storage tank. What would be more likely would-be smaller holes from pieces of the device, and there could possibly even be no holes left in the tank. The smaller holes would increase the time to form a large flammable cloud and provide firefighting teams with more time to take preventive action. 

In the case of any detonation, before the facility would be able to restart operations, it would need to conduct detailed inspections of wiring, piping, and supporting infrastructure in the affected area. The overpressure wave from the blast would be expected to loosen fitting and misalign piping and seals. Any fire in the area would require even more detailed engineering inspections to detect heat weakening of metals and damage to wiring and seals. Nearby storage tanks, particularly atmospheric tanks, would need to be checked for contamination from fumes, soot, and firefighting water and foam. 

 
/* Use this with templates/template-twocol.html */