❌

阅读视图

Is the F.A.A. Grounding the First of Many?

2026-11-20T21:23:04.199Z

Listen and subscribe: Apple | Spotify | Wherever You Listen

Sign up to receive our twice-weekly News & Politics newsletter.


The veteran transportation-safety reporter Matthew L. Wald joins Tyler Foggatt to discuss the Federal Aviation Administration’s recent nationwide grounding order, which disrupted more than ten thousand scheduled flights, and what it revealed about the vulnerabilities of the country’s aviation system. They discuss what caused the ground stop, how a seemingly minor equipment upgrade could have such far-reaching consequences, and whether responsibility lies with the Trump Administration’s cuts and disruption of the F.A.A.’s workforce or with previous Administrations’ failures to modernize the aging infrastructure. They also explore the growing role of automation in air travel, including an eight-hundred-and-seventy-five-million-dollar A.I. system being introduced by the F.A.A., and whether such innovations stand to improve aviation or introduce new risks, from user error to cyberattacks. Does this incident, along with a recent series of high-profile outages affecting technology, banking, and national-security systems, point to a growing vulnerability in the infrastructure that people rely on every day?

Recommended reading:

Tune in to The Political Scene wherever you get your podcasts.

  •  

Alta Rock Carvings in Alta, Norway

One of the most extraordinary attractions in northern Norway is Alta Museum's outdoor area, where thousands of prehistoric carvings can be found. These are not paintings or replicas displayed behind glass – they are original artworks carved directly into the bedrock by people thousands of years ago. 

Some of the carvings date back more than 7,000 years, making them among the oldest and most significant examples of prehistoric rock art in Northern Europe. They depict reindeer, bears, elk, fish, whales, boats, hunting scenes, fishing activities, human figures and mysterious rituals. The carvings were originally made near the shoreline, and as the land gradually rose after the last Ice Age, new rock surfaces became available for successive generations of artists.

Light plays an important role in discovering the carvings. Depending on the direction and angle of the sunlight, the engraved lines can become much more visible or almost disappear completely. Low-angle sunlight, especially in the morning or evening, creates small shadows inside the carved grooves, making the figures stand out more clearly.

Some of the carvings have been painted red to make them easier to see. This red colour is not original to the carvings, but was added in 1970s to help visitors recognise their shapes and details. Today, the focus is on protecting the original rock carvings while keeping modern alterations to a minimum. As part of this conservation work, the red paint is gradually being removed to preserve the site's authenticity

The site is a UNESCO World Heritage Site, recognised in 1985 for its outstanding cultural and historical importance.

  •  

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

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.

  •  

The Case for A.I. Optimism

2026-11-20T19:00:00.000Z

Listen and subscribe: Apple | Spotify | Wherever You Listen

Sign up for our daily newsletter to get the best of The New Yorker in your inbox.


In Washington, it is essential to read, or at least display, the collected works of Robert Caro. (The spines of “The Power Broker” and the multivolume biography in progress of Lyndon Johnson are compulsory in every Zoom background on cable news.) In Silicon Valley, the required reading list surely includes Richard Rhodes’s “The Making of the Atomic Bomb,” a magisterial history of the discovery of nuclear fission and its epochal resolution with the Manhattan Project and the start of the nuclear age. Not a few of the tech barons and innovators of our time see themselves as neo-Oppenheimers. When A.I. reaches maturity, it may get its Caro or Rhodes. In the meantime, Kevin Roose’s lucid journalistic account “The AGI Chronicles: The Inside Story of the Race to Create an Artificial Superintelligence” does the trick.

Roose is a classic beat reporter, having covered technology for outlets including the Times, The Atlantic, New York, and NPR. Recently, he bolted from the Times to work independently, and, these days, he is co-hosting a podcast, with Casey Newton, called “Machine Gods.” Among the most interesting A.I. podcasters around—on “Dwarkesh Podcast,” “No Priors,” and “Latent Space,” to name a few—Roose stands out for his ability to tell a story with narrative drive. He breaks things down neatly and clearly for the non-expert.

I spoke with Roose for The New Yorker Radio Hour just before Anthropic, Dario Amodei’s A.I. outfit, made what has turned out to be the largest initial public offering of all time. And, of course, while Amodei and his colleagues were coming into their many billions, Jensen Huang, the former king of the Nvidia empire, which has by many metrics powered the A.I. revolution, was appealing to his old board of directors to let him back in after his humbling. On the utopian-to-doomer scale, Roose is . . . hopeful. Or, as they say on the Sabbath Gasbag shows, cautiously optimistic. His interlocutor, by nature, is less so. We had a lot to talk about.

Anthropic is just going public. In their filing paperwork for the first half of 2026, they reported a revenue of $16.3 billion and a net loss of $80.7 billion. The company is also on the hook for $900 billion in future obligations for chips and data-center leases. How do they make the math make sense?

Basically, the bet that investors are making on Anthropic is that it will continue to grow at something close to the rate that it has been growing for the last several years. This is a company that has been growing faster than any company at its scale in the history of capitalism. Four or five years ago, they had essentially no revenue. Three years ago, they had tens of millions in revenue, and it’s been growing tenfold every year for the last three or four years. Not ten per cent; ten times.

That is due, in large part, to the popularity of their models for coding and other white-collar work. And the bet is that this growth just continues—that as these tools get better and more helpful, that more white-collar knowledge workers will incorporate them into their work, and developers will be paying much more, because usage will continue to go up.

The math doesn’t make sense if you think that A.I. is already as popular and widely adopted as it will ever be. It starts to make more sense if you anticipate that what has been happening for the past few years will keep happening—which is that the models get better and more people use them.

Some companies out here in Silicon Valley are already spending more on A.I. tokens than they are on payroll. So the long-term bet is that the economy essentially switches over from running primarily on human labor and paying human salaries to running on A.I. labor and paying token prices.

If that in fact is the right bet to make, give me a picture of the economy on an A.I. basis, as opposed to human labor. What’s it going to look like?

I think it looks a lot like my company. I’m starting a startup, Machine Gods Media. We are a six-person company right now. In our Slack, where we communicate all day, we have six humans and probably a dozen agents. And the agents are doing things we don’t know how to do ourselves. They’re writing code. I just got back from what I jokingly call our engineering department, but it’s really just a bunch of Claudes running around. They’re building tools, helping with scheduling and coördination, with all of the pieces that go into making podcasts, aside from the actual talking into a microphone.

What would those be? Is it so complex that you need Claude to do it?

It turns out to be pretty complex. For example, we have all these deliverables. When you have a show, it needs to get delivered in all these different formats. Apple needs one format, Spotify needs one format, and YouTube needs another format. And it’s all got captions, and titles, and descriptions, and metadata. And all that used to have to be done by hand. Now we have this tool that does it all for us.

Tell me how that works for a big law firm, as opposed to a six-person podcasting outfit.

It might not be a big law firm. It might actually be a small law firm, in terms of the human payroll and footprint. It might be a law firm that only has ten people, but, using A.I., they have access to essentially unlimited amounts of paralegal, junior-associate-quality labor. And so they can do, with ten people, what a more traditional firm might need a thousand people for. That may or may not be possible—there might be gaps in what these models do that might make them unsuited to that level of integration. But that’s the bet that investors are making. It’s not just that Anthropic will continue to grow or that its models will get better, but that A.I. will become the foundation of a new kind of company that will be built on top of A.I.

How many of these companies can prevail in the new world of A.I.? We have Anthropic and OpenAI, among others. Who’s in the lead and why?

Right now there are two clear frontier labs: OpenAI and Anthropic. I would say that, of the two, Anthropic may be slightly ahead; its models are considered better by some metrics. But those two are definitely the front-runners. Then there’s a small-to-medium drop-off before Google DeepMind, which to my mind is the third frontier lab. And then there’s a pretty steep drop after that—to Meta, SpaceX, the Chinese open-model companies, and some other players.

What do I get out of using Anthropic’s Claude, as opposed to OpenAI’s ChatGPT?

I use both of them—I’m pretty promiscuous. I find that some are better for some tasks than for other tasks. I use Claude to write code and to get editorial feedback on my writing. I don’t use A.I. to write, but I do use it to help me revise and edit—

As an editor, I have to stop you there. Do you get editorial feedback that is any good, as compared to when you wrote for the New York Times, or when you wrote your book?

I’ve been blessed and fortunate to have some of the most amazing human editors in my career, including at the Times and at F.S.G., where I published my book. So I hope they’re plugging their ears when they hear this next part: A.I. has gotten really good at editing.

You’re killing me here, Kevin.

I know. Look, I’m not here to tell reassuring fictions. I’m here to tell uncomfortable truths. I had a council of Claudes that would look at my chapters before I submitted them to F.S.G., and give me feedback from various perspectives. I would assign one to be the dyed-in-the-wool A.I. skeptic, and one to be an A.I. historian that knew all of the technical details about the history of these labs. And I would get the feedback in the form of these long dossiers. Maybe ninety per cent of it was crap, but ten per cent was great. My council of Claudes actually caught a few mistakes that would’ve otherwise made it into—

Whoa, whoa, whoa. Ninety per cent of the comments were crap, and you think that’s good editorial counsel?

Well, how much of what your editors give you is useful?

One hundred per cent!

[Laughs.] Well, maybe it’s just my vanity that makes me think it’s only ten per cent useful. But I do feel like, if you’re willing to wade through a bunch of subpar feedback, you can actually find good stuff in there.

The P.R. that I get is that Anthropic is the good company, as you suggest. The job interviews even have a moral dimension. Whereas OpenAI is quite a different thing. Is that fair?

That’s the image that has been portrayed.

What’s the reality?

The reality is that Anthropic and OpenAI are locked in this race together. I think we have been focussing on the wrong question with respect to these companies. I’ve spent time with Sam Altman, with Dario Amodei, and with many leaders and researchers at these companies. We in the tech press are used to asking the question of “Are the people running these companies good and trustworthy?” To my mind, that’s less useful than looking at the technology itself.

A good, moral, ethical person could still build an A.I. model that goes rogue and kills millions of people. On the other side of the coin, someone who is totally craven and corrupt could manage to produce an incredibly ethical A.I. model with all of the proper guardrails. I don’t know that it makes sense to fit the image of the founder or the C.E.O. onto the over-all impression we have of these companies.

In your book, which is fascinating, you write that a surprising number of people who work in these A.I. companies joined because they were . . . terrified. They decided that, if A.I. was going to be built, it would be better for it to be built by people who were scared, who were alarmed, who were cautious, so that the appropriate measures against disaster would be taken. Is there any evidence that these people, who are terrified, are having a significant impact within the companies—to hold them back, restrain them, to modify?

Absolutely. It’s almost impossible to imagine a counterfactual, because the companies were started by people who were terrified of A.I. Sam Altman and Elon Musk started OpenAI, in 2015, because they were scared that Demis Hassabis and Google DeepMind were going to win the race to A.G.I., artificial general intelligence. And then, several years later, Dario Amodei and six of his co-workers at OpenAI left to start Anthropic because they were terrified of the technology, and they didn’t trust Sam Altman to build it safely.

This is a recurring motif in the modern A.I. industry: people who are scared of A.I., and who don’t believe their bosses or rivals are taking enough steps to contain it, break off and start their own companies. They say, “We’re going to be the safe A.G.I. company. Those other guys are going to blow up the world if they do it, but we can be trusted.”

Some of this, it seems to me, has to do with personality, and how that personality is projected to the wider world through the press. Sam Altman projects one kind of personality, and Dario Amodei perhaps another. Tell me a little about those differences and what effect they have.

Sam Altman is a master salesman and fund-raiser. That is his superpower. From a very young age, he was a networker; he was close to major dealmakers in Silicon Valley, and extremely talented at raising money. He ran Y Combinator, the startup incubator, before leaving to become the C.E.O. of OpenAI. His reputation is that of an extremely ambitious, high-E.Q. people pleaser. As someone once told me, his superpower is being able to zero in on exactly what you want to hear and give it to you. That has served him well in some instances and poorly in others, such as when his board decided that he was lying to them and tried to fire him. It has also contributed to his reputation as somewhat two-faced or duplicitous.

What about Dario?

Dario is very high-I.Q., stubborn, and neurotic. He’s a moral absolutist, with a strong belief in what is good and right and righteous. He’s also a brilliant scientist who foresaw many of today’s A.I. trends and dynamics years before anyone else. His superpower—and his kryptonite—is that he cannot lie. Someone close to him once told me, “Dario is a guy who cannot tell a lie to save his life, which is an asset for us on even-numbered days and a liability on odd-numbered days.”

How does that work?

Sometimes it leads to him standing his ground and standing up for his principles. When the Pentagon says, “We want to use Claude for whatever we want to do,” he’s the guy who has the cojones to stand up to them, while everyone else is busy trying to snivel and get on their good side.

The Pentagon banned the use of Claude.

Yes. And a lot of people at Anthropic saw that and admired Dario for standing his ground, even when it would have been expedient for him to say whatever it took to make Pete Hegseth happy. But it also leads to these incredible moments. Remember that press briefing outside the White House, where all these A.I. C.E.O.s were standing in a semicircle? Dario was practically jumping out of his skin, unable to conceal his displeasure at having to stand alongside these cowards. He couldn’t hide it. It was written all over his face. So, I think that’s what they meant by an asset on even-numbered days and a liability on odd-numbered days.

What has stood out most for you in Anthropic’s I.P.O. and the way this has all gone?

I think about the absolute rocket-ship trajectory this company has been on, more than any other company I’ve ever covered, and perhaps more than any company that has ever existed.

The first time I visited Anthropic to report on them was three years ago. Three years—not that long ago. They had a hundred and fifty employees, working out of a cramped office in Jackson Square, in San Francisco. They didn’t even have a sign-in desk. You just took the elevator up and started walking around. They had no plans to make money. They weren’t a commercial enterprise and had barely released a product. They were a bunch of A.I.-safety-obsessed nerds who seemed genuinely worried about the technology.

If you had told me on that first visit that, three years later, this company would go public at a valuation of more than a trillion dollars and become one of the largest companies in the world, I would have laughed in your face. It seemed so unlikely that they would go from a little hundred-and-fifty-person startup to a company with, I think, more than five thousand employees, and one of the biggest in the world.

There’s perhaps a too easy confidence in the world of long-form journalism that what we do is special—that gathering information, analyzing it, and presenting it in narrative form is something A.I. simply won’t be able to do. Whereas asking for the ten best restaurants in Seattle is easy enough: you can scrape that information off the internet and present it. Are we living in a dream?

I think we are. I think there will still be a market for human-authored work—there’s just something about A.I. writing that is hollow and generic. But what’s interesting is that researchers have conducted blind tests in which people are shown two snippets of writing and asked which they prefer. Most of the time, when they don’t know which is which, people prefer the A.I.-generated work.

Really?

But when people learn which one was A.I. and which one was human-written, the preference swaps.

So, what does that tell you?

Almost everyone likes the human-written one.

They like the idea of the human-written one, but they might not innately like the human one at all.

I think the future of at least some writing will involve humans sticking their names on A.I.-generated literature because they don’t want to break that connection, that spell, with the audience.

That is not entirely reassuring, Kevin.

I’m sorry. I wish I had a rosier view.

On the continuum from doomers, people who believe A.I. will kill us all, to those who are absolutely sanguine about this whole thing—who think it’s going to be great and we’re going to work one day a week and spend the rest of our time sunning ourselves and, I don’t know, whistling—you are pretty sanguine about this subject, and the opposite of a doomer. Am I right?

I am an optimist by temperament. I believe that we can and should thread this needle, but we’ve got a lot of work to do.

What concerns you the most?

Right now, what concerns me is an intelligence explosion. That’s a term in the A.I. industry for what could happen after A.I. becomes capable of building A.I. It’s sometimes called “recursive self-improvement.” It’s the idea that an A.I. model becomes superhuman at developing other A.I. models, capable of doing the entire workload of a senior research engineer at OpenAI or Anthropic. That hasn’t happened yet, but some people, including at METR, a credible third-party organization, believe it could happen within the next year. At that point, you could use A.I., in a closed, no-human environment, to train more capable A.I. models.

What are the potential disasters, in concrete terms, that could come out of that manifestation?

If these people are right—and let’s caveat that they might not be—but if we were to see, say, a decade’s worth of improvements in A.I. capabilities compressed into a single year, because all of this could happen at machine speed rather than at human speed, I think we’d be looking at systems that start breaking a lot of things all at once. We’re already seeing some of this with cyberattacks, the incident involving Hugging Face, and the U.S. government scrambling to contain threats to critical infrastructure from these A.I. models. Imagine that, but times ten or times a hundred. There’s just a base rate of chaos and instability—

And, at the same time, a very low propensity toward regulation.

For now. But I think that could change very quickly. In fact, I believe part of the reason the Democrats won the midterms so decisively was—

Anxiety about A.I.

People had anxiety about A.I. So things could change pretty quickly on this. As unpopular as A.I. might be right now, I expect it to be even more unpopular. Right now we’re seeing this massive backlash against A.I. Unemployment is still under five per cent. It was not at all intuitive to me that we would see this level of backlash before any of the widespread job losses arrived.

Well, because you’re reading about it every two seconds, and you’re seeing reports on it on television and YouTube. There’s an anticipatory anxiety about it.

But think about how much more anxiety there would be if people were actually losing their jobs en masse. I desperately want that not to happen, but, to me, the timing of this backlash has been a little surprising, because it seems like there’s still a lot more risk out there to be priced in.

Now, I think you have to be impressed that we’ve gotten this far in our conversation without having mentioned Jensen Huang. What do you make of this? What did we just see? My God, it’s like the worst James Bond plot you have ever experienced.

It really is. It’s dime-store stuff. This is a guy who has been so central to the A.I. boom. Nvidia’s G.P.U.s are the reason we have any of this today.

Tell us what a G.P.U. is.

G.P.U. is a graphics-processing unit. Basically, a modern A.I. chip is descended from these things that gamers used to stick in their PCs to render backgrounds and polygons better. And Jensen Huang is the reason that those chips are now the most valuable commodity in the world—so valued that we’ve had to pass special export controls to prevent China from getting access to them, because, if compute is the determining factor between success and failure, we don’t want them to get our most powerful chips.

Do you figure they have it anyway?

It sure seems like they’ve gotten a bunch of them anyway. And the question is—

Thanks to Alice Huang?

Well, there’s this whole gray market of cutouts in Malaysia, Singapore, and other countries. They’ll buy a bunch of Nvidia chips because they’re allowed to buy them—they’re not China—and then they’ll either set up a data center and give Chinese companies remote access to it, or, in some cases, they’ll just smuggle the chips into China. And one of the major questions going forward is how much of this Jensen Huang knew about. Was he aware that Nvidia chips were being smuggled into China? And how much did his relationship with Alice Huang and Megaspeed factor into that?

So, what are the ramifications of this?

I mean, we’ll see where Jensen Huang ends up. He’s now saying he would like to return to Nvidia. I suspect that won’t work.

I’d like to win the Super Bowl, too, but I don’t think that’s happening.

In the short term, it means that the entire industry will have to approach things slightly differently. For many years, Jensen Huang has been the sole guy with control of the commodity that everyone in A.I. needs—the key ingredient. His relationships really determined who got how many of Nvidia’s latest chips. It was not a pure auction market. It was, like, “Oh, Alice Huang and I are friends, so I’ll save some of these chips for Megaspeed.” Or, “Elon Musk and I go way back. I’ll give him a big allotment.”

Who benefitted most from the relationship?

Elon Musk has gotten a very large allotment of chips that was maybe out of step with his company’s importance in A.I. because he and Jensen Huang are old friends. I think Sam Altman has benefitted from a close relationship with Jensen Huang.

Dario Amodei and Anthropic have actually not had a close relationship with Jensen Huang. As I reported in my book, there was a very tense meeting between Dario Amodei and Jensen Huang—it was the first time they’d met, and Jensen was basically grandstanding about how big the data center they were going to build was, while Dario was peppering him with somewhat rude questions. “Oh, how big is it going to be? What order of magnitude? Where are you going to get the power?” And eventually Dario mutters to someone sitting next to him that Jensen is acting Trump-like, and the two of them didn’t like each other for a long time.

If Dario didn’t have that kind of access for Anthropic, how has he prevailed anyway?

They have adopted a very unusual compute strategy—they have essentially gotten a little bit from everyone. They have a bunch of Amazon chips called Trainium. They rent a bunch of chips from Google, and they have a bunch of Nvidia chips, too. Rather than tethering themselves to one chip company or one hyperscaler, they have drawn from all of them to varying degrees. But they’re compute-constrained just like everyone else in the industry. They wish they had more data centers. They wish they had more chips. No one’s got enough.

I think it’s fair to say that when the internet and the iPhone first appeared we had no real concept of what an unregulated experiment on human consciousness and behavior these things would represent, on all kinds of levels—whether it was about reading, concentration, mental health, or how we related to each other. Here we are again, on the brink of another revolution that is arguably much greater—something vastly more complicated. Despite your optimism, in terms of human relations and the way we live our lives, what are you expecting in the next decade or so?

A decade is so long from now, David.

That’s fair.

I struggle to think about what the world will look like in a year.

Really?

I do. I think parts of it will look largely the same. I will still probably drop my kid off at school, go to the grocery store. There will be parts of my life that are much the same.

But when you and I talk next Thanksgiving, what will we have experienced? What changes will have been brought into our lives over the course of a year?

If the next year plays out in a way that is thoughtful, I think we will have put in place vastly more guardrails.

Where do you get your confidence that thoughtfulness is anywhere in abundance in the U.S. government, or anywhere else?

Thoughtful, or maybe just self-interested. I think we have a deep desire to remain in control of our society, of our government, of our surroundings, of our lives. We still want to be in the driver’s seat. And as long as we recognize that A.I. is not just a tool or a hype bubble but is actually, in some sense, a type of entity that could displace us at the top of the intelligence ladder . . . We could be the second-smartest thing on earth a year from now, and I think we have a lot to do between now and then. But my hope would be that we look back and say, “Wow, that was a crazy year, and a bunch of cybersecurity incidents happened, and we fixed a bunch of stuff just in time, and it was like Y2K. It could have been this major crisis, but we averted it through heroic effort and late nights at the computer terminal.” That, I think, is the good outcome.

That’s a lot of close calls to endure and still be an optimist.

We’ve done it before.

When?

Y2K, the Cold War. The Industrial Revolution played out over seventy-five or eighty years, but we muddled through. It did not lead to human extinction.

A lot of people talk about a kill switch for A.I., as if, when things get out of hand, suddenly somebody goes to a special room and turns a switch and A.I. is turned off and things can settle down, and whatever is broken can be fixed. What is a kill switch? Is it an imaginary construct or is it a real thing?

It’s an imaginary construct. I think it comes from science-fiction movies or thrillers where—

That’s where I get all my best stuff.

The red lights in the control room start blinking, and the engineer sprints over to the server rack and yanks out the cord—

Clips the blue wire instead of the red wire. Bruce Willis always chooses correctly.

Unfortunately, that is not how modern A.I. systems are running. They are distributed across huge numbers of servers and data centers. And there’s been some research into how these things can actually replicate themselves on smart devices, like smart ovens and toasters in your home. We can’t just pull the plug if it might mean taking down some huge chunk of computers across the world.

In a few years, are we going to be at twenty-five-per-cent unemployment?

I hope not. I hope we will continue to find useful and valuable things to do, but I think a lot of that depends on the decisions we make not just as a public sector, as the government, as regulators, but as employers and business leaders. I mean, do you fire your human workers as soon as they’re no longer technically adding anything to the organization, or do you retrain them for some other part of the job? I hope that we have enlightened leaders out there who will see it as part of their responsibility not to conduct layoffs as soon as it’s technically feasible.

Where does your sense of confidence, whether in the government or the private sector, reside?

My confidence resides in the public, actually. As recipients, users, and, in some cases, victims of this technology, we are not powerless or impotent. We have seen large, society-altering technological transformations turn out great, because people made it turn out great. My optimism also comes from the general belief that technology usually makes our lives better in the long run. ♦

The New Yorker Radio Hour is a co-production of WNYC Studios and The New Yorker.

  •  

A Meeting with Venezuela’s Delcy Rodríguez

2026-11-20T19:00:00.000Z

Listen and subscribe: Apple | Spotify | Wherever You Listen

Sign up for our daily newsletter to get the best of The New Yorker in your inbox.


A red text card that reads “The New Yorker Radio Hour | WNYC.”

Since the United States seized and imprisoned President Nicolás Maduro, in January, and asserted control over Venezuela’s oil production, Marco Rubio has effectively called the shots. But, rather than inviting the Trump-friendly opposition leader María Corina Machado back from exile, the U.S. elevated a loyal Maduro deputy, Delcy Rodríguez, to run a puppet regime. Who is Rodríguez, and what motivated her to make her peace with an imperial takeover? The New Yorker staff writer Jon Lee Anderson recently returned from a rare interview with Rodríguez and her brother and political consort, Jorge Rodríguez; he also spoke at length with two U.S. operatives who conceived the attack that culminated in Maduro’s abduction. He talks with David Remnick about the state of play in Venezuela, and what the Trump Administration’s designs on Cuba may be.

Further reading:

New episodes of The New Yorker Radio Hour drop every Tuesday and Friday. Follow the show wherever you get your podcasts.

The New Yorker Radio Hour is a co-production of WNYC and The New Yorker.

  •  

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

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.

  •  

Shrine of the Most Blessed Sacrement in Hanceville, Alabama

About

Extraordinary architecture designed to resemble a 13th-century Italian Franciscan church, particularly the Basilica of Saint Francis of Assisi. Marble floors, gold ornamentation, stained glass, and soaring ceilings.

The Spanish religious-art workshop Talleres de Arte Granda, founded in Madrid in 1891, designed and furnished the church's interior.

It was founded by Mother Angelica, the founder of EWTN, and opened in 1999. Three donors provided all of the funds needed for construction and completion.

Discover your next amazing Atlas Place.

Get more unusual and extraordinary places each week with the Atlas Obscura Places newsletter.

Your newsletter subscriptions with us are subject to Atlas Obscura's Privacy Policy and Terms of Use.

Community Contributors

Published

November 20, 2026

  •  

Visulahti Wax Museum in Mikkeli, Finland

Rather than being an impressive, polished wax museum, the Visulahti Wax Museum has become famous for its awkward, outdated, and sometimes unintentionally hilarious figures.

The museum has something of a cult reputation in Finland. Its wax figures are famously questionable in quality: many look surprisingly inaccurate, while some remind you more of a horror movie setting. In 1983, the Wax Museum was established with serious intentions, but nowadays people visit it mainly for nostalgic reasons. You have to approach the museum with a good sense of humour. 

The collection rarely gets updated, and the once-popular TV stars are now unfamiliar to the younger audience. The newest figurine is the Finnish president, whose resemblance – or the lack of it – has been widely discussed in the national news.

There are also international stars displayed at the museum, such as Elvis, the Beatles, and Santa Claus. At the end of the tour, a creepy version of Mickey Mouse sings to you with his friends, as you walk out of the building, wondering what you just experienced. 

  •  

The Huge Nature Reserves and Successful Wildlife Conservation Programs of Northern Tibet

China’s Chang Tang National Nature Reserve in northern Tibet is often regarded as the world’s third largest terrestrial nature reserve. Covering some 334,000 square kilometers (128,958 square miles),* it is slightly larger than Italy. But the case can be made that it is the world’s largest land-based protected area. 80-percent of top-ranking Northeast Greenland National Park, covering 972,000 square kilometers  (375,000 square miles), is covered by the Greenland icecap, an essentially lifeless area. Second-ranked Kavango–Zambezi Transfrontier Conservation Area in southern Africa is composed of 23 separate national parks and reserves in five different countries, not all of which are contiguous – or adequately protected. Chang Tang’s effective protected area, moreover, is larger than the reserve itself, as it includes several other contiguous reserves. The total size of this wildlife haven is just under 500,000 square kilometers, which is roughly the area of Spain. Put in comparative perspective, Chang Tang itself is approximately 37 times larger than Yellowstone National Park.

Map of the Main Nature Reserves of the Northern Tibetan Plateau

The Chang Tang Nature Reserve was established by the government of the Tibet Autonomous Region in 1993, around the same time that pastoral colonization efforts in the northwestern Tibetan Plateau were abandoned (see the previous GeoCurrents post). In 2000, it became a Chinese national reserve. Beijing is currently planning to transform Chang Tang into a national park, which would be the world’s largest.

Considering the brutal environmental conditions of Chang Tang, it might be assumed that little wildlife would be found there. The reserve’s average elevation is 4,800 to 5,000 meters (15,750 to 16,400 feet), which is essentially the  limit of human habitability. The region is cold, dry, and very windy. But despite these harsh conditions, a surprisingly diverse array of wildlife thrives in the reserve.

Chang Tang’s flagship species is the Tibetan antelope, or chiru, whose habitat extends upward to 5,500 meters (18,000 feet). By the 1980s, the chiru was becoming endangered, due largely to hunting pressure. As noted in the species’ Wikipedia article:

[The Chiru’s] underfur, known as shahtoosh  (a Persian word meaning “king of fine wools”), is used to weave luxury shawls. Shahtoosh shawls were traditionally given as wedding gifts in India, and it takes the underfur of three to five adult antelopes to make one shawl. Despite strict controls on the trade of shahtoosh products and CITIES listing, there is still demand for these luxury items. Within India, shawls are worth $1,000–$5,000; internationally, the price can reach as high as $20,000

According to its Wikipedia article, chiru numbers had dropped to some 70,000 by the 1990s, but rebounded to around 150,000 by 2009. Subsequently, new concerns were raised about threats posed by Chinese railroad construction across the prime remaining habitat. Recent Chinese sources, however, indicate that conservation efforts are working well, with current chiru numbers in China surpassing 300,000. Two-thirds are estimated to live in the Chang Tang region.

Several other large mammals thrive in Chang Tang. Tibetan gazelle numbers are said to be increasing, and as many as 50,000 Tibetan wild donkeys (kiang) inhabit the reserve, up from 30,000 in 1993. Wild yak populations are also mounting, rising from an estimated 7,000 in 1993 to over 10,000 today. Other large mammals found in Chang Tanginclude the Tibetan argali (a wild sheep), the blue sheep (bharal), the white-lipped deer, the snow leopard, the gray wolf, and the Tibetan brown bear. See the illustration below for range maps of most of these species. (Note: the numbers in this paragraph were derived from AI assessments.)

Range Maps of Some of the Large Mammals of China’s Chang Tang Reserve

* This figure comes from the English-language Wikipedia article on the reserve. Chinese sources generally give a slightly lower figure.

  •  

A Diagnosis Unravels Reality in “With Tapes and Toasts in the Car”

2026-11-20T11:00:00.000Z

Watch “With Tapes and Toasts in the Car.”

In 1957, Laika, a stray dog from Moscow, became the first living creature to orbit the Earth, when she was launched into space aboard the Sputnik 2. Laika was chosen as a cosmonaut dog because of her calm temperament. She died in the small spacecraft, owing to heat and stress. In Kiana Naghshineh’s animated short, a young woman named Shari flips through a magazine in her doctor’s waiting room. She sees a story about Laika, just before she goes in for an appointment, during which she receives devastating news. As Shari absorbs her new reality, she keeps imagining outer space, and Laika becomes a sort of spiritual guide; the two travel through brightly colored universes where stars and planets morph into blood vessels and cells. Naghshineh’s animation is full of bold colors and graphic shapes that are almost psychedelic, with a visual strangeness to match Shari’s world-bending, disorienting grief. As Shari spends the evening with her family, they all absorb the news and react in different ways, and, in spite of the tension that attends terrible news, they seek solace in one another.

  •  
❌