Skip to content

Category: Vulnerabilities & Advisories

Java4Shell: Critical Java Vulnerability and What to Do Now

Java4Shell is a critical vulnerability in the OpenJDK Java runtime. In the worst case, it lets attackers execute their own code using manipulated Base64 data. Java 17, 21, 25, and 27 from the major vendors are affected if they run on processors with AVX-512 VBMI. This article summarizes what is known, lists the fixed versions, and explains the measures recommended by vendors and CERTs.

Published Approx. 23 min read Author: Rootsektor Editorial Team

In short: Update Java 17, 21, 25, and 27 to 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1, respectively (or to your vendor's fixed builds), and then restart every Java process. At risk are systems with x86-64 processors that support AVX-512 VBMI, such as Intel Xeon from Ice Lake onward and AMD from Zen 4 onward; ARM64 systems are not affected. Until the update is installed, the JVM option -XX:-UseBASE64Intrinsics disables the vulnerable code path as an interim measure. Exploitation attempts have already been observed, but no successful attacks are known so far. Information as of November 19, 2026 – we will update this article as the situation develops.

What is Java4Shell?

Java4Shell is the name under which the security company Calif.io disclosed the vulnerability CVE-2026-114938. It does not reside in an application or library but in the Java runtime itself: in HotSpot, the Java Virtual Machine (JVM) of OpenJDK, on which almost all common Java distributions are built. The flaw affects an optimized routine that the JVM uses to decode Base64 data. According to Germany's Federal Office for Information Security (BSI), attackers can use manipulated input to overwrite memory, read memory contents, crash the JVM, and in the worst case execute their own code – remote code execution (BSI advisory (PDF)).

According to Oracle, Quang Luong of Calif.io and Albert Yang reported the vulnerability (Oracle CSPU November 2026). Oracle published the CVE record and rates the vulnerability 8.1 out of 10 under CVSS 3.1; it considers exploitation difficult. According to the record, an attack is possible over the network without authentication and can lead to a takeover of the Java runtime (CVE-2026-114938).

Calif, which reported the vulnerability, rates it 9.2 out of 10 under CVSS 4.0 and classifies it as critical (JFrog). According to the BSI, views on the attack complexity differ, including among the Linux distributions (BSI advisory (PDF)). Red Hat, for example, even assigns 9.8 under CVSS 3.0 and rates the vulnerability as “Critical” (Red Hat). The BSI assigns its advisory criticality level 2 (“yellow”) on a four-level scale: measures must be taken promptly (BSI advisory (PDF)).

As with php2shell, artificial intelligence plays a role. According to the BSI, research shows that AI can significantly accelerate the development of exploits (BSI advisory (PDF)). Wiz states that its AI-based research tool found the vulnerability and built a proof of concept within two hours, even before all details were public (Wiz).

The timeline:

  • January 17, 2023: Java 17.0.6 is released (Oracle). From this version on, the long-term support (LTS) release Java 17 also uses the AVX-512-accelerated Base64 decoder that had previously been developed for Java 18 (Azul, Red Hat).
  • November 17, 2026: Oracle and the OpenJDK project publish fixed versions and their security advisories (Oracle CSPU November 2026, OpenJDK advisory). The CVE record and Calif's analysis follow in the evening, Central European Time (CVE-2026-114938, Tenable).
  • November 18, 2026: The BSI, CERT-EU, and the national CERTs of France, Sweden, and Austria issue warnings (BSI advisory (PDF), CERT-EU, CERT-FR, CERT-SE, CERT.at). More vendors ship updates (details in the next section).

Which systems are affected?

A system is vulnerable only if all three of the following conditions are met (CERT-EU, JFrog):

  • Vulnerable Java runtime: OpenJDK and every distribution built on it, that is, Java 17 from 17.0.6 onward as well as Java 21, 25, and 27, unless the update released on November 17, 2026, has been installed (BSI advisory (PDF), OpenJDK advisory). The end-of-life versions 18 through 20, 22 through 24, and 26 are affected as well; they no longer receive updates (Azul, JFrog).
  • Matching processor: an x86-64 CPU with the instruction set extensions AVX-512F, AVX-512BW, AVX-512 VBMI, and BMI2. This applies, among others, to Intel Xeon processors of the Ice Lake, Sapphire Rapids, Emerald Rapids, and Granite Rapids generations and to AMD EPYC and Ryzen from Zen 4 onward. On ARM64 systems and other processors, the JVM uses a decoding path without the flaw (BSI advisory (PDF)).
  • Base64 data from outside: The application passes Base64 data controlled by an attacker to the decoder of the Java standard library. This is more common than it sounds (see How the vulnerability works).

The standard OpenJDK builds of Java 8 and 11 do not contain the vulnerable code and are therefore not affected (Red Hat, Eclipse Adoptium). There are two exceptions: Oracle lists the Java SE 8 Enterprise Performance Pack (8u511b33-perf) as affected; it is fixed in 8u513-perf (Oracle CSPU November 2026, JFrog). According to Azul, Azul Platform Prime is affected on all Java versions from Java 8 onward because its accelerated Base64 decoder does not depend on the Java version; Prime 26.08.110.0 and 26.02.510.0 are fixed (Azul). According to JFrog, Eclipse OpenJ9, the basis of IBM Semeru, is not affected (JFrog).

In its advisory, Oracle only lists the latest build of each release line as affected, for example 17.0.21.0.3. Oracle considers earlier versions of the affected releases likely to be affected as well (Oracle CSPU November 2026). What matters, therefore, is whether the fixed version is installed – not whether your build appears on Oracle's list.

Fixed versions

Fixed versions of common Java distributions (as of November 19, 2026)
VendorFixed versionsNotes
Oracle Java SE and OpenJDK17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1released on November 17, 2026 (CERT-EU)
Eclipse Temurin17.0.21.1+2, 21.0.13.1+2, 25.0.5.1+2, 27.0.1.1+4not yet available for all platforms, for example, not for Windows x64 (own research, as of the morning of November 19, 2026); the official container images will only be published once all builds of a Java version are available (Eclipse Adoptium)
Amazon Corretto17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2, 27.0.1.1.4Java on AWS Graviton (ARM64) is not affected (AWS)
Azul Zulu17.70.201, 21.54.201, 25.38.201, 27.30.201for the CPU line (subscription only): 17.69.204, 21.53.202, and 25.37.202; Zulu 8 and 11 are not affected (Azul)
Microsoft Build of OpenJDK17.0.21.1, 21.0.13.1, 25.0.5.1since November 18, 2026 (Microsoft)
BellSoft Liberica17.0.21.1+5, 21.0.13.1+5, 25.0.5.1+5, 27.0.1.1+5unscheduled releases of November 17, 2026 (BellSoft)
Red HatRed Hat build of OpenJDK 17.0.21.1, 21.0.13.1, and 25.0.5.1 as well as the RHEL packages java-17-, java-21-, and java-25-openjdksince November 18, 2026, for example RHSA-2026:100564; the Windows build of Java 25 and some container images, for example for Keycloak and JBoss EAP, are still pending (Red Hat)
Ubuntuopenjdk-17, openjdk-21, openjdk-25, and on 26.10 also openjdk-27since November 18, 2026; for 20.04 and 18.04 only via Ubuntu Pro (Ubuntu)
Debianso far only in unstablebookworm, trixie, and forky are still without an update (Debian)
SUSEupdates in preparationpackages for SUSE Linux Enterprise 15 are in quality assurance (SUSE)
Oracle GraalVM17.0.21.1, 21.0.13.1, 25.0.5.1; Enterprise Edition 21.3.20.1released on November 17, 2026 (Oracle GraalVM)

Pay attention to the full version number: vendors use different numbering schemes, and Linux distributions assign their own package versions. The relevant security advisory is what counts (BSI advisory (PDF)).

Applications and products

Because the vulnerability resides in the Java runtime, every Java application on a vulnerable JVM is potentially at risk. According to the BSI, Calif executed code without authentication on Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins, and PingFederate (BSI advisory (PDF)); according to JFrog, each of these products was running in its default configuration. With authentication, Calif also succeeded against Apache Kafka, Apache Solr, Elasticsearch, Gerrit, and Spinnaker (JFrog). Several vendors have already responded:

  • Keycloak: The official container images for 26.8 now run with a fixed Java runtime. The Keycloak version number alone does not tell you which Java version an image contains; custom images must be rebuilt on a fixed Java base image (Keycloak).
  • Jenkins: The project advises updating Java and restarting Jenkins. The Jenkins container images ship their own Java version (Jenkins).
  • Atlassian: Bamboo, Bitbucket, Confluence, Crowd, Jira, and Jira Service Management are affected in their Data Center editions. Atlassian announces out-of-band updates and provides an interim measure; Cloud customers do not need to take any action (Atlassian).
  • Elastic: Elasticsearch 7.17.3 and later is vulnerable. Only authenticated users with at least read access can execute code; without authentication, a crash is possible. Updates with a fixed Java version have been announced (Elastic).
  • Industrial and network products: Siemens lists Industrial Edge Management Pro V1, Pro V2, and Virtual as affected. No update is available yet; Siemens advises shutting down the instances or disconnecting them from the internet (Siemens SSA-272816). Cisco lists Catalyst Center and the Intersight Virtual Appliance, among others, as affected; updates for these products are still pending (Cisco).

Cloud environments

Whether a cloud server is vulnerable depends on the host's processor. Red Hat names the following, among others, as instance families that are likely affected: AWS C6i, M6i, R6i, C7i, M7i, and R7a; Google Cloud C3, C3D, C4, C4D, N4, N4D, M3, and M4; and the Azure Dsv5, Dsv6, Dasv6, and Dasv7 series (Red Hat RHSB-2026-018). The same container image can be vulnerable on one node and not on another, depending on where the platform schedules it (JFrog).

For managed services, the provider sometimes helps. As an interim measure through November 30, 2026, Google has masked AVX-512 VBMI for the managed Java 17, 21, and 25 runtimes in the App Engine standard environment and the Cloud Run second generation execution environment; you must secure other environments, such as the Cloud Run first generation or custom containers, yourself (Google Cloud). According to AWS, Lambda functions in the default execution environments are not affected, while functions on Lambda Managed Instances may be (AWS).

How the vulnerability works

The JVM compiles frequently used Java code into machine code at runtime. For particularly common tasks such as Base64 decoding, HotSpot also uses hand-written routines known as intrinsics, which rely on special processor instructions. On CPUs with AVX-512 VBMI, the JVM selects the accelerated Base64 path automatically; no special configuration is required (Red Hat RHSB-2026-018).

This path is where the flaw lies. With certain malformed input, the routine miscalculates the size of the output buffer and writes beyond the intended memory area (BSI advisory (PDF)). Google describes the cause as an integer underflow that affects the standard and the URL-safe decoder, that is, Base64.getDecoder() and Base64.getUrlDecoder() (Google Cloud).

Java does reject the malformed input with an error, but only after the out-of-bounds write has already happened. The fix is small: short remainders at the end of an input are once again handled by the safe Java implementation instead of the accelerated routine (JFrog).

One peculiarity complicates testing: the accelerated routine is only used once the C2 JIT compiler has compiled the decoding path. According to JFrog, busy services reach this point within minutes (JFrog). A clean test result shortly after startup therefore proves nothing.

What matters is whether an attacker's Base64 data reaches the decoder. Arbitrary HTTP requests are not enough; a suitable processing path is required (BSI advisory (PDF)). Such paths are common, however, and many of them are reached before authentication:

  • Authentication and sessions: HTTP Basic credentials, SAML messages, JSON Web Tokens (JWT), CSRF tokens, and cookies (Red Hat RHSB-2026-018, CERT-EU). Apache Shiro, for example, decodes its remember-me cookie using the Java standard library; updating Shiro alone therefore fixes nothing (Apache Shiro).
  • Uploads and messages: file uploads, network messages, and MIME encoded words as they appear in email headers (JFrog, Red Hat RHSB-2026-018).
  • Outbound connections: Even Java programs that do not offer a service themselves are not safe. According to Calif, a program can be attacked if it opens a TLS connection to a server controlled by an attacker (Tenable, JFrog).

Injected code runs with the privileges of the Java process, and the disclosed memory can contain credentials, private keys, and session tokens (Red Hat). According to the BSI, causing a crash is comparatively easy once a suitable processing path is reachable. For code execution, by contrast, an attacker must deliberately control the memory layout (heap grooming) and disclose memory addresses of the specific application to bypass the ASLR protection mechanism. There is therefore no universal exploit; every attack chain must be tailored to the application (BSI advisory (PDF)).

Is Java4Shell already being exploited?

Successful exploitation has not been publicly documented so far (own research, as of November 19, 2026). On November 18, 2026, the BSI wrote that the security company GreyNoise was observing initial exploitation attempts, but that no successful attacks were known and no concrete indicators of attack were available yet (BSI advisory (PDF)). Luxembourg's CERT, CIRCL, has not confirmed widespread exploitation either (CIRCL TR-104), and the European Union Vulnerability Database (EUVD) of the EU Agency for Cybersecurity (ENISA) does not list the vulnerability as exploited (EUVD-2026-127648). According to Tenable, GreyNoise has also observed scanning with a publicly available tool that checks servers for affected Java versions (Tenable).

So far, only reproductions that trigger the memory corruption without taking over a system have been published (Sysdig). Calif's proof of concept, for example, merely shows whether the flaw can be triggered with a specific combination of Java version and processor (Tenable). Calif is withholding its attack chains for individual products for now (CIRCL TR-104). Several security companies state that they have developed working exploits (Wiz, Tenable).

Because exploitation is complex, the BSI does not expect broad waves of attacks, but considers exploits for individual widely used applications likely and targeted attacks entirely realistic (BSI advisory (PDF)). CERT-EU advises updating promptly and prioritizing internet-facing applications (CERT-EU). CERT-SE also recommends checking systems for signs of intrusion (CERT-SE).

Immediate actions: update first

Only an update closes the vulnerability permanently; the BSI calls it the most effective long-term protection (BSI advisory (PDF)). Proceed in this order:

  1. Take inventory: Identify every Java runtime with its vendor and full build version – on servers, in containers, in business applications, and in appliances that ship their own Java runtime (Red Hat RHSB-2026-018). The command java -version only shows the Java version found in the search path; services and products often use a runtime of their own. On Linux, ps -eo pid,args | grep '[j]ava' shows which JVM a running process uses (CIRCL TR-104). For a container image, docker run --rm --entrypoint java <image> -version returns the version actually included, without running the image's startup command. Do not rely on image tags: in the official images, the tag 17.0.21 still denotes a vulnerable build for Eclipse Temurin. For Amazon Corretto, the same tag has only pointed to the fixed build since November 17, 2026; images pulled or built on it earlier remain vulnerable (own research, as of November 19, 2026). A well-maintained SBOM, the bill of materials of your software and third-party products, makes the search easier.
  2. Check processors: On Linux, grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$' shows whether the CPU meets the requirements; a system is at risk if all four features appear (BSI advisory (PDF)). Check on the host or node where the application actually runs (Keycloak). Use the result only to set priorities: after a migration or a change of instance size, the same application can end up on a processor with AVX-512 VBMI (JFrog, CIRCL TR-104).
  3. Update: Install Java 17.0.21.1, 21.0.13.1, 25.0.5.1, or 27.0.1.1 according to your version, or your vendor's fixed builds from the table above. If you still run one of the end-of-life versions 18 through 20, 22 through 24, or 26, move to a supported version. For the Java SE 8 Enterprise Performance Pack, the fixed version is 8u513-perf; for Azul Platform Prime, it is 26.08.110.0 or 26.02.510.0.
  4. Restart and rebuild: After the update, every Java process must be restarted (BSI advisory (PDF), CERT-EU). Rebuild container images on fixed base images. For products with their own Java runtime, use the vendor's update path instead of replacing the JVM yourself (Red Hat RHSB-2026-018).
  5. Ask your vendors: For appliances, hosted services, and third-party products, the update is the vendor's responsibility. Such products remain vulnerable until the vendor delivers a fixed version (CERT-EU). Ask your vendors, and follow their advisories.

If you cannot update right away, the following interim measures reduce the risk but do not replace the update:

  • Disable Base64 acceleration: Start the JVM with -XX:-UseBASE64Intrinsics. The option disables only the accelerated Base64 path, which is why Red Hat considers it the preferred option (Red Hat RHSB-2026-018); the BSI and Eclipse Adoptium also mention it (BSI advisory (PDF), Eclipse Adoptium). Base64 processing becomes slower as a result – according to Azul, possibly much slower for large amounts of data (Azul). Set the option where the JVM reads its startup parameters: in the startup script (Eclipse Adoptium), in the product's options file, for example for Elasticsearch (Elastic), or via the JAVA_TOOL_OPTIONS environment variable (Apache Shiro). Remove the option again after the update (Red Hat RHSB-2026-018).
  • Alternative: -XX:UseAVX=2 disables AVX-512 entirely and can also reduce performance (CERT-EU); Azul recommends this option for applications that process a great deal of Base64 (Azul). Only set it on x86-64: JVMs on ARM64 do not recognize it and then fail to start (Red Hat RHSB-2026-018). Google and Atlassian therefore combine it with -XX:+IgnoreUnrecognizedVMOptions (Google Cloud, Atlassian).
  • Verify the effect: Check on the running JVM whether the option is in effect: jcmd <PID> VM.flags -all | grep -E 'UseBASE64Intrinsics|UseAVX' shows the active values (CIRCL TR-104). With the first option, the line for UseBASE64Intrinsics must show the value false; with the second, the line for UseAVX must show the value 2. An environment variable that has been set is not proof on its own (Red Hat RHSB-2026-018, Keycloak).
  • Test first, then roll out: Try every option on a single system first. Sysdig warns, for example, that the alternative -XX:DisableIntrinsic=_base64_decodeBlock prevents the JVM from starting without an additional unlock option. Rolled out fleet-wide via JAVA_TOOL_OPTIONS, it takes entire services down (Sysdig).
  • Restrict access: If neither the update nor a JVM option is possible right away, temporarily allow access to affected Java applications only from trusted networks. Internet-facing services that process Base64 input before authentication take priority (BSI advisory (PDF)).
  • Do not overestimate filters: A web application firewall and request buffering can make individual attack paths harder but do not provide complete protection (BSI advisory (PDF)). CIRCL considers input validation and size limits for Base64 data merely an additional layer of protection (CIRCL TR-104).

Detecting signs of an attack

According to the BSI, there are no concrete indicators of attack yet; operators should monitor internet-facing Java applications more closely for anomalies (BSI advisory (PDF)). CERT-SE and security researchers point to these signals:

  • unapproved Java runtimes, unexpected JVM crashes, and suspicious Java processes (CERT-SE)
  • JVM crash logs (hs_err_pid*.log files), segmentation faults (SIGSEGV), and bursts of service restarts (Sysdig)
  • the error message IllegalArgumentException: Input byte array has wrong 4-byte ending unit in application logs; according to Sysdig, researchers saw it on every attack attempt in their tests (Sysdig)
  • follow-up activity, such as Java processes that start a shell, drop and run programs, or open new connections (Sysdig)
  • hits from network signatures: Cisco Talos provides Snort rules that detect malformed Base64 data in certain fields of HTTP requests (Cisco Talos)

A single crash or error message does not prove an attack, because faulty clients also produce invalid Base64 data. Search your logs in a targeted way, including older entries – for example, for unusual Authorization headers in requests (Sysdig). Do not check whether production systems are affected by using publicly available attack code or deliberately triggered crashes; CIRCL advises against this as well (CIRCL TR-104).

If an internet-facing service ran with a vulnerable JVM on a matching processor, check after the update whether credentials, keys, and tokens need to be rotated – the vulnerability can also disclose memory contents. If you have a concrete suspicion, a compromise assessment clarifies whether attackers left traces. If an attack is already visible, report the emergency directly to our team.

Not sure where Java runs in your environment? A vulnerability assessment examines your systems from the outside and, with authenticated scans, from the inside. It identifies installed Java versions and prioritizes the findings. A web application penetration test shows where your web applications process Base64 data before authentication; we examine software developed in-house in a secure code review.

Checklist: working through Java4Shell

  • Every Java runtime is inventoried with its vendor and full version, including in containers, business applications, and appliances
  • The processors of hosts and cloud instances have been checked; the result is used only for prioritization
  • Java 17, 21, 25, and 27 are on 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1, respectively, or on the vendor's fixed build; the end-of-life versions 18 through 20, 22 through 24, and 26 have been replaced
  • Every Java process has been restarted, and container images have been rebuilt and verified in the running container
  • Vendor statements are available for appliances and third-party products, and the updates are scheduled
  • Where the update has not yet been installed, the JVM verifiably runs with -XX:-UseBASE64Intrinsics or -XX:UseAVX=2, or access is limited to trusted networks
  • Logs have been checked for JVM crashes, unusual Base64 errors, and suspicious Java processes
  • Credentials, keys, and tokens on exposed systems have been assessed and rotated where necessary

Conclusion: update, restart, know your inventory

Java4Shell does not affect just one application; it affects the Java runtime underneath. Whether a system is vulnerable depends on the interplay of Java version, processor, and application – and in the cloud, that can change with every restart. Apply the updates everywhere instead of searching for supposedly safe systems, and put internet-facing services and authentication systems first. No successful attacks are known so far, but the BSI considers exploits for individual widely used applications likely.

In the long run, patch management that also covers bundled Java runtimes pays off. Oracle now releases security updates on the third Tuesday of every month; the next ones are due on December 15, 2026 (Oracle CSPU November 2026).

Sources

All sources accessed on November 19, 2026.

Frequently asked questions

Are Java 8 and Java 11 affected by Java4Shell?

Not in the standard OpenJDK builds: Java 8 and 11 do not contain the vulnerable Base64 decoder. The exceptions are Oracle's Java SE 8 Enterprise Performance Pack, fixed in 8u513-perf, and Azul Platform Prime, which according to Azul is affected on all Java versions from Java 8 onward. An update is worthwhile anyway: in the same release, the OpenJDK project fixed other vulnerabilities that also affect Java 8 and 11 (OpenJDK advisory).

Do workstations and laptops need to be updated as well?

Yes, as soon as Java runs on them; they are vulnerable if the processor meets the requirements. In addition to Intel Xeon, the BSI lists AMD Ryzen from Zen 4 onward (BSI advisory (PDF)). According to VulnCheck, Intel desktop and laptop processors from 2019 to 2021 (Ice Lake, Tiger Lake, Rocket Lake) also support the required instructions, while Intel has disabled AVX-512 in its client processors since the 12th generation (VulnCheck). Java programs that connect to third-party servers are particularly at risk; according to Calif, a TLS connection to a malicious server is enough (Tenable). Therefore, update every Java runtime on clients as well, including those bundled with programs.

How reliable is the JVM option as an interim measure?

The option -XX:-UseBASE64Intrinsics disables the vulnerable code path; Red Hat recommends it until the update is installed, and the BSI and Eclipse Adoptium also list it as an interim measure. However, it only works if the running JVM has actually applied it. Check this with jcmd, as described in the section on immediate actions. Oracle and the OpenJDK project do not mention this option in their advisories (Tenable); only the update provides lasting protection.

What does Java4Shell have to do with Log4Shell?

Apart from the similar name, not much. Log4Shell, discovered in late 2021, was a flaw in the Log4j logging library that applications ship with. Java4Shell, by contrast, resides in the Java runtime itself. Updating individual libraries therefore does not help; what matters is the version of the JVM on which an application runs.

Share article

Contact

Not sure whether your Java systems are affected?

We help you locate vulnerable Java runtimes in your environment, prioritize the updates, and check your systems for traces of a possible attack.

Get in touch+49 2932 465265-0

Author

Rootsektor Editorial Team

Team of Rootsektor IT-Security GmbH

Under this name, the team of Rootsektor IT-Security GmbH publishes articles on vulnerabilities, attack techniques, and defense. The company offers vendor-independent penetration testing, security services, and incident response and forensics, and is editorially responsible for the articles.

About Rootsektor

Transparency note: This article was created with the support of AI tools. Editorial responsibility for its content and statements lies with Rootsektor IT-Security GmbH.

Related services

Glossary terms

Blog

More articles

All articles
  • Vulnerabilities & Advisories

    php2shell: Critical PHP Vulnerabilities and What to Do Now

    · Approx. 12 min read

    Two critical flaws in the PHP core let attackers run code on web servers without authentication. Which versions are affected, how the vulnerabilities work, and what you need to do now.