❌

普通视图

  • ✇Cloudflare Blog
  • How Cloudflare WAF protects against ruby2shell (CVE-2026-132825) Daniele Molteni · Pawel Klimek · Denzil Correa
    On November 19, 2026, the Ruby team disclosed ruby2shell (CVE-2026-132825), a heap buffer overflow in the way Ruby changes the case of strings. Ruby rates the flaw Critical and says it is aware of proofs of concept that achieve remote code execution in some scenarios. Fixes shipped in Ruby 3.3.14, 3.4.13, and 4.0.10.The reach is wide. Veria Labs reports that Ruby on Rails and classic-style Sinatra applications reach the bug in their default configuration, before any authentication. Self-hosted
     

How Cloudflare WAF protects against ruby2shell (CVE-2026-132825)

2026年11月21日 04:24

On November 19, 2026, the Ruby team disclosed ruby2shell (CVE-2026-132825), a heap buffer overflow in the way Ruby changes the case of strings. Ruby rates the flaw Critical and says it is aware of proofs of concept that achieve remote code execution in some scenarios. Fixes shipped in Ruby 3.3.14, 3.4.13, and 4.0.10.

The reach is wide. Veria Labs reports that Ruby on Rails and classic-style Sinatra applications reach the bug in their default configuration, before any authentication. Self-hosted products that bundle Ruby, including GitLab, GitHub Enterprise Server, Mastodon, OpenProject, Discourse and Chatwoot, shipped an affected Ruby in their latest release at the time of disclosure.

Cloudflare WAF blocks ruby2shell for all customers, including those on the Free plan. We have added two rules to both the Cloudflare Free Managed Ruleset and the Cloudflare Managed Ruleset, with Block as the default action: one for ruby2shell and one for GHSA-87fm-7w84-j2px, a related integer overflow in Ruby string case conversion fixed in the same releases.

The WAF is a compensating control, not a replacement for patching. Exploits can reach the bug through paths a WAF does not see, and the only complete fix is to upgrade Ruby. Our team continues to monitor attack traffic and will update the rules as new techniques appear. You can track rule changes in the WAF changelog and get the latest on the vulnerability in the Cloudflare Zero Wire briefing.

Cloudflare has patched its own systems that use Ruby, and we have found no indication of compromise.

What we know about ruby2shell

Ruby strings carry an encoding, and Ruby still supports many legacy single-byte encodings, such as ISO-8859-1 (Latin-1) and Windows-1252, alongside UTF-8. In a single-byte encoding each character takes one byte, so changing the case of a string usually produces output of the same length.

The German sharp s (ß) breaks that assumption. Its uppercase form is two characters, SS. In 14 ISO-8859 and Windows-125x encodings, Ruby writes those two bytes but checks for room for only one. According to Veria Labs, a string with 21 sharp s characters overflows the output buffer by one byte. The methods that reach the bug are upcase, swapcase, downcase(:fold) and casecmp?. UTF-8 strings take a different code path and are not affected.

A one-byte overflow can look harmless. In a memory-corruption exploit, though, a single byte written past the end of a heap buffer can be enough to corrupt an adjacent object or allocator metadata. Ruby says it is aware of proofs of concept that turn this flaw into code execution, and Veria Labs says it will publish its own proof of concept about a week after disclosure. We expect scanning to start soon after.

Why default Rails and Sinatra apps are exposed

HTML forms can only send GET and POST requests. To simulate PUT, PATCH, or DELETE, many web frameworks accept a _method parameter in a POST request. Rack, the interface most Ruby web frameworks build on, implements this in its MethodOverride middleware, which converts the value of _method to uppercase. Rails includes this middleware by default, and classic-style Sinatra applications enable it. An attacker can send a multipart POST request whose _method part declares a legacy character set and contains a run of sharp s characters. The framework upcases the value while it is still routing the request, before any application code or authentication check runs.

Veria Labs reports that other frameworks and plain Rack applications are not exposed by default. Application code that changes the case of strings received in a legacy encoding may still be affected, wherever the string comes from.

Who is affected

Condition

Details

Ruby version

Ruby 3.3.13 and earlier, 3.4.0 through 3.4.12, and 4.0.0 through 4.0.9. Veria Labs reports the bug has been present since Ruby 2.4.0. Ruby 3.2 and earlier have reached end of life and will not receive the fix.

Framework

Rails and classic-style Sinatra in their default configuration. Any other code that changes the case of attacker-controlled strings in a legacy single-byte encoding.

Bundled software

As of November 19, 2026, Veria Labs lists GitLab 19.6.0, GitHub Enterprise Server 3.22.5, Mastodon 4.7.5, OpenProject 17.9.7, Discourse 2026.10.1 and Chatwoot 4.20.0 as bundling an affected Ruby in their latest release. Discourse moved its Docker base image to Ruby 4.0.10 on November 19, so rebuilding a Docker install picks up the fix.

Distribution packages can backport fixes without changing the Ruby version number, so check the full package version against your distribution's advisory.

Six more Ruby flaws in the same release

Ruby 3.3.14, 3.4.13, and 4.0.10 also fix six other memory safety flaws, and Ruby says several of them can lead to code execution. One, GHSA-87fm-7w84-j2px, is an integer overflow in the same string case conversion code, and our second WAF rule covers it. The other five are in Ruby's regular expression engine. Most of them require the application to compile or match a regular expression pattern supplied by the attacker. That is uncommon in web applications, but it does happen in search features, filtering rules and admin tools.

How Cloudflare WAF protects you

Upgrading every Ruby runtime takes time, especially when Ruby is bundled inside self-hosted products and container images. Cloudflare WAF reduces your exposure while you patch.

New managed rules, on for every customer

Both rules are part of the Cloudflare Free Managed Ruleset and the Cloudflare Managed Ruleset (Ruleset ID efb7b8c949ac4650a09736fc376e9aee), with Block as the default action.

Rule description

Rule ID

Ruleset

Default action

Ruby - Heap Overflow - CVE:CVE-2026-132825

7328f23691e44b07892ebd25b19210f1

Cloudflare Free Managed Ruleset (Free plan)

Block

Ruby - Heap Overflow - CVE:CVE-2026-132825

1afa543a1ed84893b01df04c34402c88

Cloudflare Managed Ruleset (Pro, Business and Enterprise plans)

Block

Ruby - Integer Overflow - GHSA-87fm-7w84-j2px

8660e37e86444f9f9267ba22e9855f05

Cloudflare Free Managed Ruleset (Free plan)

Block

Ruby - Integer Overflow - GHSA-87fm-7w84-j2px

6defac6a52334542adf4a162daf25922

Cloudflare Managed Ruleset (Pro, Business and Enterprise plans)

Block

On the Free plan, the Cloudflare Free Managed Ruleset runs automatically, so there is nothing to turn on. On paid plans, the rules are active wherever the Cloudflare Managed Ruleset is deployed. Because paid plans give you more control over how rulesets are deployed, the Cloudflare Managed Ruleset may not be active on every zone. We recommend checking its status to confirm that it is running. You can use the links in the Zero Wire briefing to go straight to the rules in your dashboard.

What the WAF cannot see

A WAF can block an exploit when the malicious input arrives in an HTTP request that passes through Cloudflare. It cannot block every path to the vulnerable code:

  • Traffic that bypasses Cloudflare. Requests sent directly to your origin IP address, and traffic between internal services, never reach the WAF. Configure your origin to accept traffic only from Cloudflare, for example with Cloudflare Tunnel or Authenticated Origin Pulls.
  • Other entry points into the same code. Ruby code that changes the case of strings from email, file imports, message queues or background jobs can reach ruby2shell without an HTTP request.

Adding defense in depth with WAF attack score

Memory corruption is usually only the first step. To run commands, an attacker still has to deliver a second-stage payload, such as shell commands or a reverse shell, and then interact with the compromised server. WAF attack score uses machine learning to score each request for remote code execution payloads, which helps catch exploit variations and post-exploitation traffic that signature-based rules can miss. Create a custom rule that blocks or challenges requests with cf.waf.score.rce le 20 on Enterprise plans, or cf.waf.score.class eq "attack" on Business plans.

Impact on Cloudflare infrastructure

Cloudflare has patched its systems that use Ruby against ruby2shell. We have found no indication of compromise and continue to monitor.

Patch now

ruby2shell turns a one-byte miscalculation in string case conversion into a pre-authentication path to code execution in default Rails and Sinatra apps. With a public proof of concept expected within days, the window to patch is short. Here is what to do:

  1. Check your WAF coverage. On the Free plan, the ruby2shell rules are already blocking. On paid plans, confirm the Cloudflare Managed Ruleset is deployed and the rules have not been overridden.
  2. Upgrade Ruby to 3.3.14, 3.4.13 or 4.0.10 and restart every Ruby process, including background workers. Rebuild container images. Move applications on Ruby 3.2 or earlier to a supported series.
  3. Update self-hosted products that bundle Ruby, such as GitLab, GitHub Enterprise Server, Mastodon, OpenProject and Chatwoot, as each vendor releases a fix. Rebuild Discourse Docker installs now.
  4. Inventory your runtimes. The Zero Wire briefing includes a prompt you can give an AI agent to find every affected Ruby runtime in your infrastructure.

Our WAF analysts will keep updating protections as new techniques appear. Follow the WAF changelog for rule updates.

How Cloudflare WAF helps protect against phpAfterShell and other critical PHP flaws

2026年11月21日 04:00

On November 19, 2026, the security research company depthfirst disclosed phpAfterShell (CVE-2026-126714), a vulnerability in PHP's default file-based session handler that can lead to remote code execution. Under the Common Vulnerability Scoring System (CVSS) 4.0, it scores 9.2 out of 10 (Critical). The PHP project fixed it the same day in versions 8.2.36, 8.3.37, 8.4.28, 8.5.13, and 8.6.0. These releases fix 16 other security vulnerabilities, six of them also rated critical.

Cloudflare’s web application firewall (WAF) blocks known phpAfterShell attack patterns, including for customers on the Free plan. The protection comes from a PHP remote code execution rule we first deployed in October 2026 for the php2shell vulnerabilities. That rule already detected part of the phpAfterShell attack pattern before the vulnerability was disclosed, and on November 19 we updated its detection logic to cover phpAfterShell. The rule is part of both the Cloudflare Free Managed Ruleset and the Cloudflare Managed Ruleset, is enabled by default, and its default action is Block.

In the same WAF release, we added three new rules to the Cloudflare Managed Ruleset for paid plans: one for a request smuggling flaw in PHP-FPM (CVE-2026-129289), and two for flaws in PHP's SOAP extension (CVE-2026-15353 and CVE-2026-129506) that PHP fixed in the same releases. These rules are enabled by default with the Log action, because the request patterns they look for can also appear in legitimate traffic, and blocking by default could disrupt it. Customers can review matching requests in Security Events now and change the action to Block once they confirm the rules do not affect legitimate traffic.

The WAF is an additional layer of defense, not a replacement for the patch. Several of the critical flaws depend on server configuration or can be reached through paths a WAF does not see, and the only complete fix is to upgrade PHP and restart every worker. Our analysts continue to monitor attack activity and will update the rules as new techniques and variations appear. You can track rule changes in the WAF changelog and follow how the vulnerabilities develop in the dedicated Cloudflare Zero Wire briefing.

There appears to be no indication so far that these vulnerabilities have been exploited. As of November 19, 2026, none of the 17 vulnerabilities was listed in CISA's Known Exploited Vulnerabilities catalog, and no source we reviewed reports exploitation in the wild.

What we know about phpAfterShell

PHP stores session data in files by default. When an application calls session_start(), PHP reads the session file and deserializes its content into the $_SESSION array. When the request ends, PHP writes the updated session back to the same file.

phpAfterShell is triggered when that write is interrupted. The session file can then hold the beginning of the new session data followed by the end of the old one. On the next request, session_start() deserializes this mixed content. If an attacker controlled the old data, PHP can end up deserializing objects of the attacker's choice.

An attacker trying to exploit the flaw is likely to first search for a way to place controlled data in the session. PHP's advisory names two:

  • Session upload progress, a PHP feature that writes information about a running file upload into the session. A remote client can use it to shape the stored data.
  • Applications that store large user-controlled strings in the session.

According to PHP, code execution also requires an interruption at a useful point in the write and a suitable deserialization gadget chain in the application. depthfirst reports that it reached code execution without an application gadget by chaining a second, undisclosed memory-corruption bug in a PHP-native class. The sources we reviewed do not establish whether that second bug is fixed in the November 19 releases.

depthfirst says it discovered and reported phpAfterShell. The CVE record credits Leo Lin and Asahi as reporters.

The other critical flaws

The same releases fix six more critical vulnerabilities. Each one needs a specific configuration to be exploitable:

CVE

Component

Impact

Conditions

CVE-2026-129289

PHP-FPM

An unauthenticated attacker can smuggle a second FastCGI request into PHP-FPM and run PHP code as the worker.

A front end that reuses backend FastCGI connections (nginx with fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on, or HAProxy), an application path that opens php://input without reading it to the end, and the path of an existing PHP script.

CVE-2026-115560

Session serializer

Object injection through a mismatch between session serializers. First covered in our php2shell briefing, now fixed.

Session upload progress enabled. PHP widened the scope: applications, pools or command-line jobs that use different serializers and share a session store are affected.

CVE-2026-129496

Timezone cache

Use-after-free that can crash a fresh worker and possibly run code. PHP demonstrated code execution locally with known memory addresses.

Non-thread-safe builds where a startup diagnostic has been written to a PHP error log file.

CVE-2026-129481

Session shutdown

Use-after-free, described by PHP as an incomplete fix for CVE-2026-109619. No code execution demonstrated.

PHP 8.3 and later.

CVE-2026-129474

Fatal error backtraces

Use-after-free in magic method backtraces.

PHP 8.5 and later, where fatal error backtraces are enabled by default. Setting zend.exception_ignore_args=1, the php.ini-production default, blocks the demonstrated attack.

CVE-2026-129182

Fatal error backtraces

Use-after-free. No code execution demonstrated.

PHP 8.5, specific path-level settings, and an Apache per-directory configuration or front end that produces an early diagnostic.

Who is affected

The vulnerable versions are PHP 8.2 before 8.2.36, 8.3 before 8.3.37, 8.4 before 8.4.28, 8.5 before 8.5.13, and the 8.6.0 release candidates. Whether a deployment is exposed depends on the conditions of each flaw.

PHP 8.1 and earlier are end-of-life. depthfirst says the official 7.4, 8.0 and 8.1 end-of-life mitigation branches are not affected by phpAfterShell, but PHP says CVE-2026-129289 was introduced in PHP 5.6.0 and that releases older than 8.2 may also be affected by CVE-2026-115560.

Linux distributions often backport fixes without changing the PHP version number. Check the full package version against your distribution's advisory.

How Cloudflare WAF protects you

PHP runs a large share of the web, often inside content management systems, plugins, and container images that teams do not update directly. Patching every PHP runtime takes time. Cloudflare WAF reduces your exposure while you patch.

phpAfterShell: protection on every plan

We released the original PHP remote code execution rules in an emergency release on October 21, 2026, after the php2shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619) were disclosed. We extended them to CVE-2026-115560 on October 23 and refined them several times in the following weeks, based in part on reports from security researchers who took part in a PHP Capture the Flag (CTF) challenge.

phpAfterShell shares an attack technique with php2shell: an attacker plants serialized PHP data in session storage and waits for PHP to deserialize it. Because of that overlap, the existing rule already matched part of the phpAfterShell attack pattern before disclosure. On November 19, we updated the rule's detection logic to cover phpAfterShell and added CVE-2026-126714 to its description.

Rule description

Rule ID

Ruleset

Default action

PHP Remote Code Execution Attack (CVE-2026-109618, CVE-2026-109619, CVE-2026-115560, CVE-2026-126714) #6

19373a83abb840e18ab3ce5a7975ce1b

Cloudflare Free Managed Ruleset (Free plan)

Block

PHP Remote Code Execution Attack (CVE-2026-109618, CVE-2026-109619, CVE-2026-115560, CVE-2026-126714) #6

4148ae686fdb4d01be673fab9d9c073d

Cloudflare Managed Ruleset (Pro, Business and Enterprise plans)

Block

Free plan customers do not need to take any action. On paid plans, the rule is active wherever the Cloudflare Managed Ruleset is deployed. You can use the links in the Zero Wire briefing to go straight to the rules in your dashboard.

New rules for PHP-FPM and SOAP flaws

The three new rules are part of the Cloudflare Managed Ruleset (Ruleset ID efb7b8c949ac4650a09736fc376e9aee) and are available on Pro, Business and Enterprise plans.

Rule description

Rule ID

Default action

PHP-FPM - CVE:CVE-2026-129289

8ef1c34a424b4ccfa6f6fe186c6f42b2

Log

PHP SOAP - CVE:CVE-2026-15353

5c5a9d6397e44837a3214b5ba54028d4

Log

PHP SOAP - CVE:CVE-2026-129506

00a23de67a684876ba67c5d44521b819

Log

To review their matches, go to Security > Analytics > Events and filter by rule ID. If the matches are not legitimate traffic, change the rule action to Block: go to Security > Settings, edit the Cloudflare Managed Ruleset, search for the CVE identifier and set the rule action to Block, or you can refer to the links in the Zero Wire briefing to go straight to the rules configuration.

What the WAF cannot see

A WAF can block an exploit when the malicious data arrives in an HTTP request that passes through Cloudflare. It cannot block every path to these vulnerabilities, including:

  • The deserialization step. phpAfterShell's final step happens inside PHP, when it reads a corrupted session file. The WAF can block the requests that plant the payload, not the read itself.
  • Session data from other sources. If an application copies user-controlled data into the session from a database, a queue or an upstream API, that data may never cross the WAF in a recognizable form.
  • Flaws triggered by server state. CVE-2026-129496, CVE-2026-129481, CVE-2026-129474 and CVE-2026-129182 depend on error logs, diagnostics and worker lifecycle. They do not have dedicated WAF rules, and the patch and the configuration changes below are the way to address them.
  • Traffic that bypasses Cloudflare. This includes internal traffic between services and PHP-FPM listeners exposed directly to a network.

Adding defense in depth with WAF attack score

WAF attack score adds a machine learning layer that scores each request for attack payloads. It is available on Business plans (cf.waf.score.class) and, with a dedicated remote code execution sub-score (cf.waf.score.rce) along with an overall score (cf.waf.score), on Enterprise plans.

Attack score complements the managed rules. It will not recognize every serialized object or smuggled FastCGI record on its own, but a working exploit chain usually needs more than one request, and the later stages carry payloads the model is trained to score:

  • Second-stage payloads. Once an attacker can run code, they still need to send commands: shell execution primitives (/bin/sh -c, system(), passthru()), PHP code evaluation (eval(), assert()) or reverse-shell strings in headers, query parameters or request bodies.
  • Webshell traffic. Attackers often drop a small PHP webshell after the initial compromise. Requests that pass operating system commands to that webshell remain visible to attack score.

Deploy protections and patch

You can find more information on how to deploy managed rules and attack score in our WAF guide. In short:

  1. Check that phpAfterShell protection is active. On the Free plan, no action is needed. On paid plans, make sure the Cloudflare Managed Ruleset is deployed and that the PHP Remote Code Execution Attack #6 rule is set to Block.
  2. Review the new rules and switch them to Block. The CVE-2026-129289, CVE-2026-15353 and CVE-2026-129506 rules are in Log mode by default. Review their matches in Security Events, then change their action to Block.
  3. Layer attack score. Create a custom rule that blocks or challenges requests with a low remote code execution score, for example cf.waf.score.rce le 20 on Enterprise plans, or cf.waf.score.class eq "attack" on Business plans.
  4. Upgrade PHP. Move to 8.2.36, 8.3.37, 8.4.28, 8.5.13 or 8.6.0. Rebuild container images and restart the PHP-FPM master or Apache so every worker loads the new binary, then verify the version that serves web requests. After upgrading, check that no php.ini, FPM pool or virtual host still sets session.upload_progress.enabled=1, because an explicit setting overrides the new default.
  5. Apply interim mitigations if you cannot upgrade right away. Set session.upload_progress.enabled=0 and limit the untrusted data you store in sessions. Turn off FastCGI connection reuse. On PHP 8.5, set fatal_error_backtraces=0. Fix configuration errors that produce PHP startup warnings, or send PHP errors to syslog instead of a file. Keep PHP-FPM listeners off untrusted networks. These steps reduce exposure; they do not fix the flaws.

For a prompt you can give an AI agent to inventory your PHP deployments and check each one against all seven critical CVEs, see the phpAfterShell page on Cloudflare Zero Wire.

Update every PHP runtime now

phpAfterShell turns an interrupted file write in PHP's default session handler into a path to code execution, and it arrived in the same release as six other critical flaws. With technical details now public, we expect exploit attempts to follow. Cloudflare WAF blocks known phpAfterShell attack patterns for every customer, including the Free plan, and paid plans have new rules for the PHP-FPM and SOAP flaws. The fix is still to upgrade PHP and restart the services that use it.

  • ✇LWN.net
  • Security updates for Friday jzb
    Dist. ID Release Package Date AlmaLinux ALSA-2026:98525 9 bind9.18 2026-11-20 AlmaLinux ALSA-2026:98521 9 bubblewrap 2026-11-19 AlmaLinux ALSA-2026:98503
     

Security updates for Friday

作者 jzb
2026年11月20日 21:52
Dist. ID Release Package Date
AlmaLinux ALSA-2026:98525 9 bind9.18 2026-11-20
AlmaLinux ALSA-2026:98521 9 bubblewrap 2026-11-19
AlmaLinux ALSA-2026:98503 9 fence-agents 2026-11-20
AlmaLinux ALSA-2026:98508 9 freerdp 2026-11-20
AlmaLinux ALSA-2026:98541 9 grafana 2026-11-20
AlmaLinux ALSA-2026:99172 9 grafana-pcp 2026-11-20
AlmaLinux ALSA-2026:100479 8 gstreamer1-plugins-bad-free 2026-11-20
AlmaLinux ALSA-2026:100478 9 gstreamer1-plugins-bad-free 2026-11-20
AlmaLinux ALSA-2026:98493 9 jackson-core 2026-11-20
AlmaLinux ALSA-2026:98492 9 jackson-databind 2026-11-20
AlmaLinux ALSA-2026:100563 8 java-17-openjdk 2026-11-19
AlmaLinux ALSA-2026:100564 9 java-17-openjdk 2026-11-19
AlmaLinux ALSA-2026:100568 10 java-21-openjdk 2026-11-19
AlmaLinux ALSA-2026:100567 8 java-21-openjdk 2026-11-19
AlmaLinux ALSA-2026:100567 9 java-21-openjdk 2026-11-19
AlmaLinux ALSA-2026:100572 10 java-25-openjdk 2026-11-19
AlmaLinux ALSA-2026:100571 9 java-25-openjdk 2026-11-19
AlmaLinux ALSA-2026:100662 9 kernel 2026-11-20
AlmaLinux ALSA-2026:100729 8 kernel-rt 2026-11-20
AlmaLinux ALSA-2026:99720 10 mysql8.4 2026-11-19
AlmaLinux ALSA-2026:99741 9 mysql:8.4 2026-11-20
AlmaLinux ALSA-2026:98535 9 qt5-qtbase 2026-11-20
AlmaLinux ALSA-2026:98531 9 qt5-qtdeclarative 2026-11-20
AlmaLinux ALSA-2026:98509 9 raptor2 2026-11-20
AlmaLinux ALSA-2026:98494 9 resteasy 2026-11-20
AlmaLinux ALSA-2026:100735 8 sos 2026-11-20
Debian DLA-4920-1 LTS electrum 2026-11-19
Debian DLA-4918-1 LTS nginx 2026-11-19
Debian DSA-6642-1 stable nginx 2026-11-19
Debian DLA-4917-1 LTS openjdk-17 2026-11-19
Debian DLA-4919-1 LTS pam-mysql 2026-11-19
Debian DSA-6643-1 stable pam-mysql 2026-11-19
Debian DLA-4916-1 LTS php8.2 2026-11-19
Debian DSA-6641-1 stable php8.4 2026-11-19
Fedora FEDORA-2026-3a9945b706 F44 aws 2026-11-20
Fedora FEDORA-2026-e4e90c5ff2 F45 aws 2026-11-20
Fedora FEDORA-2026-59352ce434 F44 bind9-next 2026-11-20
Fedora FEDORA-2026-95b54d6bad F45 bind9-next 2026-11-20
Fedora FEDORA-2026-490a0000af F44 blender 2026-11-19
Fedora FEDORA-2026-1d60977d78 F45 c-ares 2026-11-19
Fedora FEDORA-2026-36c0aba2e1 F43 composer 2026-11-20
Fedora FEDORA-2026-ab2aaea969 F44 composer 2026-11-20
Fedora FEDORA-2026-479af584c3 F45 composer 2026-11-20
Fedora FEDORA-2026-04383cf016 F43 dr_libs 2026-11-20
Fedora FEDORA-2026-4708e42849 F44 dr_libs 2026-11-20
Fedora FEDORA-2026-3205211f60 F45 dr_libs 2026-11-20
Fedora FEDORA-2026-666b7444a4 F43 et 2026-11-20
Fedora FEDORA-2026-8272c43689 F44 et 2026-11-19
Fedora FEDORA-2026-67db247b7f F45 et 2026-11-19
Fedora FEDORA-2026-42fa7b1577 F45 gh 2026-11-19
Fedora FEDORA-2026-db7a3ef92b F43 incron 2026-11-20
Fedora FEDORA-2026-4b67d2e4ac F44 incron 2026-11-20
Fedora FEDORA-2026-93de20052b F45 incron 2026-11-20
Fedora FEDORA-2026-2302c5a427 F45 libXfont2 2026-11-19
Fedora FEDORA-2026-7a8986960b F43 libaec 2026-11-20
Fedora FEDORA-2026-74b55bb1ca F44 libaec 2026-11-19
Fedora FEDORA-2026-d787efae91 F45 libfontenc 2026-11-19
Fedora FEDORA-2026-93ccf43a01 F43 mtools 2026-11-20
Fedora FEDORA-2026-374f630522 F45 nebula 2026-11-19
Fedora FEDORA-2026-78e97e818b F43 perl-Imager 2026-11-20
Fedora FEDORA-2026-9754401c44 F44 perl-Imager 2026-11-19
Fedora FEDORA-2026-619249be30 F45 perl-Imager 2026-11-19
Fedora FEDORA-2026-66a5101223 F45 perl-Text-JSCalendar 2026-11-20
Fedora FEDORA-2026-faa459c7ef F45 perl-Text-JSContact 2026-11-20
Fedora FEDORA-2026-58508b648e F43 php 2026-11-20
Fedora FEDORA-2026-fc441e91d2 F44 php 2026-11-19
Fedora FEDORA-2026-d34e6fa12f F45 php 2026-11-19
Fedora FEDORA-2026-cbdf2a98ef F43 python-loguru 2026-11-20
Fedora FEDORA-2026-848bbd442b F43 python3.6 2026-11-20
Fedora FEDORA-2026-5a90f8090a F44 python3.6 2026-11-20
Fedora FEDORA-2026-eaec9934c0 F45 python3.6 2026-11-20
Fedora FEDORA-2026-c85076ba3e F44 qpid-proton 2026-11-20
Fedora FEDORA-2026-b8fd91440f F45 qpid-proton 2026-11-20
Fedora FEDORA-2026-8ba6632f4a F43 roundcubemail 2026-11-20
Fedora FEDORA-2026-f67031546e F44 roundcubemail 2026-11-20
Fedora FEDORA-2026-b6615c7ae7 F45 roundcubemail 2026-11-20
Fedora FEDORA-2026-d5bf5d11a8 F44 runc 2026-11-20
Fedora FEDORA-2026-531ddf5058 F45 runc 2026-11-20
Fedora FEDORA-2026-94fa41e927 F43 xen 2026-11-20
Gentoo 202611-13 PHP 2026-11-19
Gentoo 202611-12 Ruby 2026-11-19
Gentoo 202611-11 nginx 2026-11-19
Mageia MGASA-2026-0602 10 hplip 2026-11-19
Oracle ELSA-2026-99142 OL9 .NET 10.0 2026-11-19
Oracle ELSA-2026-92511 OL8 .NET 11.0 2026-11-19
Oracle ELSA-2026-99054 OL8 .NET 11.0 2026-11-19
Oracle ELSA-2026-99138 OL9 .NET 11.0 2026-11-19
Oracle ELSA-2026-99052 OL8 .NET 8.0 2026-11-19
Oracle ELSA-2026-99146 OL9 .NET 8.0 2026-11-19
Oracle ELSA-2026-99051 OL8 .NET 9.0 2026-11-19
Oracle ELSA-2026-99144 OL9 .NET 9.0 2026-11-19
Oracle ELSA-2026-98521 OL9 bubblewrap 2026-11-19
Oracle ELSA-2026-99160 OL9 emacs 2026-11-19
Oracle ELSA-2026-99111 OL9 firefox 2026-11-19
Oracle ELSA-2026-98536 OL9 flatpak-builder 2026-11-19
Oracle ELSA-2026-98115 OL8 gcc 2026-11-19
Oracle ELSA-2026-98532 OL9 gimp 2026-11-19
Oracle ELSA-2026-98512 OL9 glibc 2026-11-19
Oracle ELSA-2026-98541 OL9 grafana 2026-11-19
Oracle ELSA-2026-99172 OL9 grafana-pcp 2026-11-19
Oracle ELSA-2026-99228 OL9 gstreamer1 2026-11-19
Oracle ELSA-2026-98513 OL9 gvfs 2026-11-19
Oracle ELSA-2026-95609 OL8 java-1.8.0-openjdk 2026-11-19
Oracle ELSA-2026-95613 OL9 java-1.8.0-openjdk 2026-11-19
Oracle ELSA-2026-100563 OL8 java-17-openjdk 2026-11-19
Oracle ELSA-2026-100564 OL9 java-17-openjdk 2026-11-19
Oracle ELSA-2026-100567 OL8 java-21-openjdk 2026-11-19
Oracle ELSA-2026-100567 OL9 java-21-openjdk 2026-11-19
Oracle ELSA-2026-100571 OL9 java-25-openjdk 2026-11-19
Oracle ELSA-2026-61752-0 OL7 libssh2 2026-11-19
Oracle ELSA-2026-98981 OL9 mod_http2 2026-11-19
Oracle ELSA-2026-99215 OL9 perl-CGI 2026-11-19
Oracle ELSA-2026-99162 OL8 perl-DBI 2026-11-19
Oracle ELSA-2026-99208 OL9 perl-DBI 2026-11-19
Oracle ELSA-2026-99210 OL8 perl-DBI:1.641 2026-11-19
Oracle ELSA-2026-98533 OL9 python3.9 2026-11-19
Oracle ELSA-2026-99593 OL9 rpm 2026-11-19
Oracle ELSA-2026-98537 OL9 squid 2026-11-19
Oracle ELSA-2026-98514 OL9 tesseract 2026-11-19
Oracle ELSA-2026-100540 OL8 thunderbird 2026-11-19
Oracle ELSA-2026-99623 OL8 tigervnc 2026-11-19
Oracle ELSA-2026-98538 OL9 tigervnc 2026-11-19
Oracle ELSA-2026-98519 OL9 util-linux 2026-11-19
Oracle ELSA-2026-99132 OL9 webkit2gtk3 2026-11-19
Oracle ELSA-2026-98530 OL9 xdg-dbus-proxy 2026-11-19
Red Hat RHSA-2026:99726-01 EL8.4 compat-openssl10 2026-11-19
Red Hat RHSA-2026:99725-01 EL8.6 compat-openssl10 2026-11-19
Red Hat RHSA-2026:99724-01 EL8.8 compat-openssl10 2026-11-19
Red Hat RHSA-2026:1703-01 EL9.6 kernel 2026-11-19
Red Hat RHSA-2026:100744-01 EL10 nginx 2026-11-20
Red Hat RHSA-2026:100748-01 EL9 nginx 2026-11-20
Red Hat RHSA-2026:100747-01 EL8 nginx:1.24 2026-11-20
Red Hat RHSA-2026:100746-01 EL9 nginx:1.24 2026-11-20
Red Hat RHSA-2026:100750-01 EL9.8 nginx:1.24 2026-11-20
Red Hat RHSA-2026:100745-01 EL9 nginx:1.26 2026-11-20
Red Hat RHSA-2026:75864-01 EL10 nodejs22 2026-11-19
Red Hat RHSA-2026:84703-01 EL10.0 nodejs22 2026-11-19
Red Hat RHSA-2026:75870-01 EL8 nodejs:22 2026-11-19
Red Hat RHSA-2026:76750-01 EL9 nodejs:22 2026-11-19
Red Hat RHSA-2026:84589-01 EL9.6 nodejs:22 2026-11-19
Red Hat RHSA-2026:98121-01 EL6 openssl 2026-11-19
Red Hat RHSA-2026:96220-01 EL7 openssl 2026-11-19
Red Hat RHSA-2026:96216-01 EL9.4 openssl 2026-11-19
Red Hat RHSA-2026:98096-01 EL10.0 python-urllib3 2026-11-19
Red Hat RHSA-2026:90759-01 EL8 python-urllib3 2026-11-19
Red Hat RHSA-2026:90494-01 EL9 python-urllib3 2026-11-19
Red Hat RHSA-2026:98126-01 EL9.2 python-urllib3 2026-11-19
Red Hat RHSA-2026:98125-01 EL9.4 python-urllib3 2026-11-19
Red Hat RHSA-2026:98122-01 EL9.6 python-urllib3 2026-11-19
Red Hat RHSA-2026:92474-01 EL8 python3.12-urllib3 2026-11-19
Red Hat RHSA-2026:98097-01 EL9.4 python3.12-urllib3 2026-11-19
Red Hat RHSA-2026:98098-01 EL9.6 python3.12-urllib3 2026-11-19
Red Hat RHSA-2026:99149-01 EL9.8 qt5-qtbase 2026-11-20
Red Hat RHSA-2026:99155-01 EL10.2 qt6-qtbase 2026-11-20
Slackware SSA:2026-323-01 gnutls 2026-11-19
Slackware SSA:2026-323-02 perl 2026-11-19
Slackware SSA:2026-323-03 php 2026-11-19
SUSE SUSE-SU-2026:24788-1 SLE-m6.1 cifs-utils 2026-11-19
SUSE SUSE-SU-2026:24785-1 SLE-m6.1 elemental-operator, elemental-system-agent, elemental- toolkit 2026-11-19
SUSE SUSE-SU-2026:24790-1 SLE-m6.1 haproxy 2026-11-19
SUSE SUSE-SU-2026:5380-1 SLE12 java-11-openjdk 2026-11-19
SUSE SUSE-SU-2026:5381-1 SLE15 java-11-openjdk 2026-11-20
SUSE SUSE-SU-2026:24791-1 SLE6.0 SLE-m6.0 SLE-m6.1 kernel 2026-11-19
SUSE SUSE-SU-2026:24786-1 SLE-m6.1 libXi 2026-11-19
SUSE SUSE-SU-2026:24789-1 SLE-m6.1 python-M2Crypto 2026-11-19
SUSE SUSE-SU-2026:24792-1 SLE-m6.1 python-oauthlib 2026-11-19
SUSE SUSE-SU-2026:5379-1 SLE15 oS15.4 rekor 2026-11-19
SUSE SUSE-SU-2026:5382-1 SLE15 oS15.6 xen 2026-11-20
Ubuntu USN-9165-1 26.10 kernel 2026-11-19
Ubuntu USN-9170-1 18.04 20.04 linux, linux-aws, linux-aws-5.4, linux-azure, linux-bluefield, linux-fips, linux-gcp, linux-gcp-5.4, linux-gcp-fips, linux-hwe-5.4, linux-ibm, linux-ibm-5.4, linux-iot, linux-kvm, linux-oracle, linux-raspi, linux-raspi-5.4, linux-xilinx-zynqmp 2026-11-19
Ubuntu USN-9171-1 14.04 16.04 18.04 linux, linux-aws, linux-aws-fips, linux-aws-hwe, linux-azure, linux-azure-4.15, linux-azure-fips, linux-fips, linux-gcp, linux-gcp-4.15, linux-gcp-fips, linux-hwe, linux-kvm, linux-oracle 2026-11-19
Ubuntu USN-9173-1 22.04 24.04 linux, linux-aws, linux-aws-fips, linux-gcp, linux-gcp-6.8, linux-gke, linux-gkeop, linux-ibm, linux-ibm-6.8, linux-oracle-6.8, linux-vmware 2026-11-19
Ubuntu USN-9172-1 14.04 16.04 linux, linux-aws, linux-fips, linux-kvm, linux-lts-xenial 2026-11-19
Ubuntu USN-9167-1 20.04 22.04 linux, linux-aws, linux-gcp, linux-gcp-5.15, linux-gke, linux-gkeop, linux-ibm, linux-ibm-5.15, linux-oracle 2026-11-19
Ubuntu USN-9166-1 24.04 26.04 linux, linux-aws, linux-gcp, linux-gcp-7.0, linux-gke, linux-ibm, linux-oem-7.0, linux-vmware 2026-11-19
Ubuntu USN-9169-1 20.04 linux-aws-5.15 2026-11-19
Ubuntu USN-9168-1 22.04 linux-aws-fips, linux-kvm 2026-11-19
Ubuntu USN-9170-2 20.04 linux-aws-fips 2026-11-19
Ubuntu USN-9168-2 22.04 linux-fips, linux-gcp-fips 2026-11-19
Ubuntu USN-9174-1 24.04 linux-gcp-fips 2026-11-19
Ubuntu USN-9171-2 16.04 linux-oracle 2026-11-19
Ubuntu USN-9175-1 24.04 linux-oracle 2026-11-19
Ubuntu USN-9182-1 14.04 16.04 18.04 20.04 22.04 24.04 26.04 26.10 nginx 2026-11-20
Ubuntu USN-9178-1 26.04 26.10 openjdk-17-crac 2026-11-20
Ubuntu USN-9179-1 26.04 26.10 openjdk-21-crac 2026-11-20
Ubuntu USN-9180-1 26.04 26.10 openjdk-25-crac 2026-11-20
Ubuntu USN-9181-1 16.04 18.04 20.04 22.04 24.04 26.04 26.10 openjdk-8 2026-11-20
Ubuntu USN-9177-1 22.04 24.04 26.04 pyjwt 2026-11-20
Ubuntu USN-9176-1 22.04 24.04 26.04 26.10 ruby3.3, ruby3.2, ruby3.0 2026-11-19

The LWN site is currently under high scraper load, so comment display has been suppressed for anonymous users. If you are a human, you may read the comments by clicking the button below:

Note: you can avoid this step in the future by logging into your LWN account.

  • ✇The New Yorker
  • The Former Trump Official Who Thinks Trump’s Staff Has Let Him Down
    2026-11-20T11:00:00.000ZSave this storySave this storyIn his new book, “The President Deserves Better: Leadership and Accountability to Keep America Great,” John Ullyot argues that President Donald Trump’s advisers and appointees have let him down in his faltering second term. As Ullyot, a former deputy assistant to Trump at the White House who has held several government jobs during Trump’s Administrations, including as chief spokesman for the National Security Council,
     

The Former Trump Official Who Thinks Trump’s Staff Has Let Him Down

2026年11月20日 20:06
2026-11-20T11:00:00.000Z

In his new book, “The President Deserves Better: Leadership and Accountability to Keep America Great,” John Ullyot argues that President Donald Trump’s advisers and appointees have let him down in his faltering second term. As Ullyot, a former deputy assistant to Trump at the White House who has held several government jobs during Trump’s Administrations, including as chief spokesman for the National Security Council, writes “The bottom line is this: The President deserves better.” He adds, “And it’s not just from his Cabinet Secretaries. Many individuals and groups work behind the scenes to block or slow-roll Trump’s reform agenda. You often hear about how liberal media outlets and the foot-dragging, antireform, bureaucratic Deep State try to stop Trump. This book provides a first-hand account of how that happens on a day-to-day basis.”

Recently, in The Atlantic, Ullyot called for the resignation of Defense Secretary Pete Hegseth, whom he had advised at the Pentagon in 2025, saying that Hegseth had mismanaged the Iran war and was becoming an embarrassment to the President. (In April of that year, Ullyot detailed the chaos at the Pentagon under Hegseth in Politico.) I recently spoke by phone with Ullyot about his time working with Trump, and the source of the problems in the President’s Administration. Our conversation, edited for length and clarity, is below.

I read your Atlantic piece calling for Hegseth’s resignation. What is it that you think he has done wrong?

Hegseth has done a lot of damage to the Pentagon and to the military. I volunteered to stand up his press operation just for a short period of time at the start of his term last year, and he and I got along very well. When I left, as planned, after standing up his operation and turning it over to his friend—a friend of his that he had selected to run the operation—he thanked me for doing a good job, et cetera. And then it was after that that things got very crazy. I didn’t notice a lot of crazy things going on when I was there, but it was after that point, after I left, that I decided to write that op-ed in Politico. And that was because things had gotten so crazy that he had two of my friends marched out of the building by security, and he accused them of leaking material to the press, and he just had become very paranoid about the leaks.

Hegseth is the least qualified and most polarizing Defense Secretary in modern memory. And as a Marine veteran, and as someone who has spent a lot of time in both the Senate Armed Services Committee and at the National Security Council working with senior members of the military and senior Pentagon leaders, I felt the need to speak out, because he was doing real damage and it was hurting the President as well.

He was appointed to the job by President Trump, right?

Yes.

So how do you understand President Trump’s decision to appoint him, and also to keep him in the job, even as he’s doing this tremendous damage that you referenced?

So, the President hired him. In his first term, President Trump hired people based on recommendations from many people who were outsiders. And he felt, I believe, that he was not well served by several of them. In his second term, it has been different. He’s hired more on loyalty and hired more people who are going to pursue his agenda rather than those who have a résumé.

So is Hegseth pursuing Trump’s agenda?

I think he is in a lot of ways. The President decided to go to war in Iran, and the Secretary reportedly pushed him into that. I do not think that the President has paid attention to the damage that Hegseth has done on either the cultural front or the self-promoting front, or to the damage that he’s done in taking out very good leaders of the military. I think that the President is mainly briefed on what’s going on at the Pentagon by Pete Hegseth, and doesn’t have people around him who have apprised him of the job that Hegseth’s doing and the damage that he’s done.

If Trump could focus a little more, sit down, read a briefing book on what Hegseth was doing, it might be easier to get him to come around to what you’re saying.

Yeah, I think that’s right. But I really do think that the President hired Hegseth without really looking under the hood. He watches Fox News a lot, and Hegseth, he’s very bombastic, outspoken; he really shouts into the camera on Fox News. And I think President Trump said, “Hey, this guy must be a real military hero. He’s a man’s man, et cetera.” I doubt that he looked at his résumé much, because a lot of people are surprised that Hegseth was not a SEAL Team Six door-kicker or something like that. But he has a persona, and he wrote three books about lethality in the military. I read all three of them before going to work for him.

Oh, wow.

Yeah, and basically they all say the same thing, and they can be summed up with one page: The military’s gone woke. And, No beardos, no weirdos, no trannies, no fatties, this type of thing.

Did that message appeal to you when you first joined the Administration, but then you thought, Oh, maybe the “no beardos, no weirdos” thing is not actually the way to carry out the running of the Pentagon?

I wrote an op-ed back when Hegseth was still in high school, when I left the Marine Corps, about the need to keep high physical standards, because that was going out, particularly with integrating women into Marine units. Anyway, so I’m not agreeing with him. He’s not the person who invented the idea of high physical standards. And then, in terms of his criticism of how identity politics were woven into the military, I agreed with that. But I wouldn’t make it a big deal. I would just get it done. So I didn’t think you needed to beat your chest about restoring . . . whether it’s in any government position, I agree with eliminating identity politics or identity-based hiring. So I was on board with both of those, but I wasn’t screaming about it.

“Talk softly and carry a big stick” kind of thing.

Yeah, just make the changes and don’t make a big deal about it.

It does occur to me that people who write books that, as you say, can be summarized by lines like “No beardos, no weirdos” might not be so laser-focussed on really running the department as well as they should, and might be more focussed on being obnoxious and things like that. I don’t know. I’m just speculating.

Yeah, I think that’s right. I mean, with his résumé and his bombast, I think that he was probably qualified to be the Pentagon spokesperson, or since he spends a lot of time P.T.ing with the troops, he could have been head of the Presidential physical-fitness council, like Arnold Schwarzenegger was. But, actually, you need a manager or somebody with real management experience to run the largest department in the federal government.

Let’s just go back to President Trump, because your book is very interesting on this idea that Trump has been let down by the people around him in his second term. Is the problem Hegseth, or is the problem more that Trump didn’t do his due diligence?

I don’t think he did due diligence. I think President Trump just saw him on Fox News, liked what he saw, and didn’t say, O.K., let’s look into his background.

Is that then the fault of people around Trump, or is it more Trump’s fault? Because your book is saying that Trump himself is a very effective leader, but that he’s been let down. So I’m curious how you think that through.

So I think that ultimately the buck stops with the President. So, when I say the President deserves better, yes, he deserves better from his staff, but above all he deserves better from himself. Let’s say you’re a friend of a pro golfer and the pro golfer knows that he can do better. You would say, “Hey, look, I think you deserve better than that. You deserve to train a little more or to work on your swing with a swing coach,” et cetera. It’s not a great analogy.

No.

Like any C.E.O., the President is the steward of his own brand. And his brand has slipped badly. But he needs to have staff that are not yes-men. He never did this in the first term, but if you look at these scripted or televised Cabinet meetings where they’ll go on for an hour, the Cabinet meetings with the cameras rolling, they’ll just go around while all the Cabinet members are trying to outdo each other. Each Cabinet member’s trying to outdo the others in praising the President. And that’s not serious. The President doesn’t need that, but ultimately he’s responsible.

Trump’s first Cabinet meeting, in 2017, five months into his term, included a lot of praise, if I remember correctly.

Well, I mean, that could have been the case, but now every Cabinet meeting is televised. I mean, in the first term there were some serious people there who were supporters of the President, but they were not seal clappers the way you see a lot in this Administration.

I am looking now, and in June of 2017, at that first Cabinet meeting, they did go around the room praising him. But, as you say, there’s going around the room and praising him, and then there’s going around the room and really praising him. So you have to draw distinctions, which I think is what you are trying to do.

That’s right. I’ve been in and out of the private sector and advise C.E.O.s, and I say a good C.E.O. surrounds himself with people who are strong enough to tell him what he doesn’t want to hear. And one of them that I worked with was Alan Mulally, when he was C.E.O. of Ford, and they were doing the auto-bailout hearings, back in December of 2008. Mulally was great to work with, and, famously, when he took over Ford, he had his first review of the business units and all the charts, and he said, “Put a green, yellow, or red chart based on how your business unit is doing.” So it was all green while the company was losing billions. And then one executive finally put up a red slide, and Mulally just started applauding him, and later that executive became C.E.O. and replaced Mulally. Mulally wanted to hear the bad news, probably before the good news.

Does it seem to you that Trump wants to hear the bad news before the good news?

No, I don’t think so. I think he deserves better from himself on that. He deserves to look under the hood much more than he has been doing in his second term.

Your book is about how the President deserves better from his staff, but it seems like one of the things you’re saying in this conversation is that the President deserves better from himself, which is a little different.

Yes, that’s right. He made three promises when I worked for him as a senior adviser on the 2016 campaign: no more forever wars, drain the swamp, and put America first. In his first term, when I worked for him in the White House, he was new to Washington and very laser-focussed on delivering on those priorities.

When I remember the first term, it was a lot of tweeting in the middle of the night. It was a lot of staying in the residence to watch Fox News. It was a lot of golfing. I’m not saying things are exactly the same as this term, but when you say the President was laser-focussed on his priorities, I’m trying to remember that.

No, you’re right about his tweeting and his watching TV and staying up late. That hasn’t changed, but what I think has changed in this second term is that he has lost focus on implementing his promises.

I think the ballroom is distracting him. Honestly, I think that’s one of the problems.

Yeah, exactly. So, anyway, things slipped in the second term. Now you’ve got former aides who are cashing in on his name.

Is he cashing in, too, do we think?

I don’t think he is, but certainly there are allegations that his family is. I mean, I think that he’s not personally—

Oh, so you think it’s more his family than him?

Well, it’s his family, but it’s also, let’s look at the ballroom or the library. He is building these big projects that need a lot of money, and so any donor to any President does not contribute to their projects five years after they’ve been President. They’re all lining up to contribute when the President has the power. But, in draining the swamp, that was his promise to be a different President, and now you’ve got his aides.

But do you think that flows from the top? Maybe this gets back to what you say about the fact that he himself deserves better. Maybe he should tell himself to tell his family not to focus on business deals.

Right. This was not a visible embarrassment in the first term. Now it’s a visible embarrassment, and, in fact, he’s reportedly surprised by some of these revelations. So, when we come back to “the President deserves better,” he should have set the tone in the second term and said, “No more of this B.S., I’m different. That’s why I was elected in 2016, because people wanted me to drain the swamp, and I don’t want to have anybody, whether it’s my family or anybody else, riding on my name.”

I think one important thing about your book is getting the message out there that he needs to do this.

Yeah. I appreciate that. That’s what I was trying to do in writing the book. And I had no idea when I started writing it a year and a half ago that the Republican Party would take the shellacking that it did. I mean, nine Senate seats. I worked in the Senate for seven years, and nine seats is seventeen per cent of all the senators. I looked it up—seventeen per cent of the entire collection of senators in the chamber.

Wouldn’t nine Senate seats be nine per cent of the Senate?

Of the Republicans. Republicans had fifty-three. If you divide nine out of fifty-three—

Of course, yeah, my mistake.

Yeah, no worries. So, anyway, nine seats is a lot of seats. Anyway, when I started writing this book, I was saying it is maybe intended for future Presidents, but now it has become a lot more relevant to this President.

Well, honestly, if there’s a theme to this conversation, I think it’s that if Trump had read Hegseth’s books, or if he reads your book now, things could be better. Maybe Trump reading more books is the solution here.

Yeah, maybe that’s the solution.

Last question for you: What if someone said, “Look, this Donald Trump, he’s got a little older, he’s surrounded by more loyalists, but fundamentally, this is the guy who, from the start, talked about Obama’s birth certificate, and then he talked about ‘Mexican’ judges, and then he insulted people all the time, and there are all these accusations about how he assaults women, and then there were all these things that he said about Haitians, and January 6th, and then you go to the second term, and he’s posting the video of the Obamas as apes, and actually he is just the same guy who never really had any sense of how to run the country or a sense of the national interest”? I’m not saying there’s any merit to this idea, but what do you think of it?

Well, no, I think that’s a very good point. What I would say is he’s the same man, but, politically, voters were once willing to overlook this pugilistic, crude character tweeting about the Obamas as apes and all of that business.

It seems as if you wish Trump would remind himself, and remind people, that fundamentally he was a businessman who came to shake up Washington. If he could get back to that, maybe he could get back on the right track.

Yeah, absolutely. There’s still a runway for him to get things done. ♦

❌
Subscriptions