CME FedWatch September 2026: What a 56% Rate-Hike Probability Means for Your SEC Disclosures

The CME FedWatch Tool is showing a 56% probability of a 25-basis-point rate hike at the September 16, 2026 FOMC meeting. Three weeks ago, the market was pricing a 70% chance of no change. That kind of single-event repricing is not just a trading story. For CFOs, IR teams, and compliance officers, it is a disclosure trigger that needs a decision before the next filing window closes.

Every top-ranking result on this topic is aimed at crypto traders. None of them address what finance professionals actually need to know: whether this probability shift changes your SEC disclosure obligations, how to characterize it accurately in MD&A, and which accounting standards it touches. This article fills that gap.

Key takeaway: A market-implied rate-hike probability crossing 50% at a specific FOMC meeting is not just a market data point. For companies with variable-rate debt, interest-rate-sensitive assets, or floating-rate derivatives, it almost certainly qualifies as a known uncertainty requiring updated MD&A discussion under SEC Regulation S-K Item 303.

What CME FedWatch Actually Measures (and What It Doesn't)

CME FedWatch derives rate-change probabilities from 30-Day Fed Funds futures prices, not from surveys, polls, or Fed communications. It reflects the aggregate positioning of interest-rate traders on the CME exchange. The tool does not represent a Fed forecast, a consensus economist view, or a commitment from any FOMC member.

CME Group is explicit about this. Their official disclaimer states: "The data and output from this tool does not constitute investment advice and is not a personal recommendation from CME Group. Decisions based on this information are the sole responsibility of the relevant investor."

For disclosure purposes, this characterization matters. When your MD&A, earnings call script, or investor presentation references FedWatch, it must describe the figure as a market-implied probability derived from futures pricing, not as a prediction or forecast. CME Group also requires proper attribution: "MEDIA: Please attribute rate probabilities used in your reporting to 'CME FedWatch.'" That attribution requirement extends to corporate communications.

The practical implication: a sentence like "the Fed is expected to raise rates in September" is not supported by FedWatch. A sentence like "as of late September 2026, CME FedWatch, which derives probabilities from 30-Day Fed Funds futures, showed a 56% market-implied probability of a 25bp hike at the September 16 FOMC meeting" is accurate and defensible.

How the September 2026 Repricing Happened

Before Fed Chair Kevin Warsh's keynote at the Jackson Hole symposium, the market assigned nearly 70% probability to no change at the September 16 meeting. That flipped to a 56% probability of a 25bp hike within hours of the speech, according to Yahoo Finance's reporting on CME FedWatch data.

Warsh's remarks were the catalyst. He said that "better-than-expected summer inflation readings did not demonstrate that underlying trends had meaningfully improved" and that the Fed needed "confidence that underlying inflation was moving toward its objective clearly and quickly enough." That language is unambiguously hawkish, and futures markets repriced immediately.

The repricing was not isolated to one instrument. Kalshi prediction markets moved to 48% probability of a hike, Polymarket to 49%, and the 2-year Treasury yield reached its highest level since late July 2026 following the speech. Cross-market convergence across Fed Funds futures, SOFR-linked instruments, and prediction markets strengthens the signal that this was a genuine reassessment, not noise in a single market.

The macro backdrop explains why the speech landed so hard:

• PCE inflation: 3.7% YoY through June 2026
• Core PCE: 3.3% YoY through June 2026
• June unemployment: 4.2%
• July 2026 employment report: net job losses
• FOMC July 2026 meeting: three members dissented in favor of a hike

That last point deserves attention. Three FOMC dissenters is an unusually high number. It signals a committee that was already closer to a hike than the headline "hold" decision suggested. For disclosure purposes, the dissent record increases the uncertainty range around the September outcome and should inform how companies frame their interest-rate risk narrative.

Fed Governor Lisa D. Cook captured the genuine ambiguity in an August 5, 2026 speech: "I am prepared to support a rate increase if necessary," while also noting that "disinflationary forces could move inflation toward the Fed's target without an increase." That dual-sided assessment from a voting FOMC member is exactly the kind of policy uncertainty that MD&A disclosures should reflect, not a one-sided rate-hike narrative.

Does a FedWatch Probability Shift Trigger SEC Disclosure Obligations?

The short answer is: it depends on your company's interest-rate exposure, but for many companies the answer is yes.

SEC Regulation S-K Item 303 requires companies to discuss known trends, demands, commitments, events, or uncertainties that are reasonably likely to have a material effect on financial condition or results of operations. A near-coin-flip probability of a 25bp hike at a specific meeting is a known uncertainty. For companies with significant variable-rate debt, floating-rate derivatives, or interest-rate-sensitive pension obligations, the materiality threshold is almost certainly crossed.

The SEC has consistently emphasized that MD&A should be forward-looking and decision-useful. A generic "interest rates may rise" risk factor is not sufficient when FedWatch is pricing a greater than 50% probability of a specific hike at a specific meeting. Companies should quantify the potential impact: what does a 25bp increase do to annual interest expense, debt service coverage ratios, and fair values?

Here is a framework for assessing your disclosure obligations:

The 8-K question is harder. A shift in FedWatch probability alone does not constitute a reportable event under Form 8-K. But if the probability shift, combined with your company's specific exposure, produces a material change in financial condition or results, the analysis changes. Companies with very large floating-rate debt loads or significant interest-rate derivative positions should document why they concluded an 8-K was or was not required. That documentation protects you in a subsequent SEC comment letter review.

For a deeper walkthrough of the specific ASC 815, ASC 320, and Item 305 implications of rate-hike probability shifts, see our earlier analysis: Fed Rate Hike Probability at 69%: What Your Q2 2026 10-Q Must Say About Interest Rate Risk.

How to Write MD&A Interest-Rate Risk Disclosure When the Outcome Is a Coin Flip

The worst MD&A disclosure in this environment is a static boilerplate paragraph that ignores the September 16 meeting entirely. The second-worst is a paragraph that asserts a rate hike as a certainty when the market is pricing a 56% probability.

The right approach reflects genuine uncertainty while being specific about the company's exposure. A well-constructed MD&A interest-rate risk section in the current environment should:

1. State the current rate environment accurately. The Federal Reserve has held the federal funds rate at 3.50% to 3.75% since December 2025. As of late September 2026, CME FedWatch, which derives probabilities from 30-Day Fed Funds futures, showed a market-implied probability of approximately 56% for a 25bp hike at the September 16, 2026 FOMC meeting.
2. Quantify your exposure. For every 25bp increase in the benchmark rate, annual interest expense increases by $X million based on $Y million of variable-rate debt outstanding as of [date].
3. Acknowledge the committee's internal division. Three FOMC members dissented in favor of a hike at the July 2026 meeting, indicating a committee closer to action than the headline hold decision suggested.
4. Reference the macro backdrop without overstating it. PCE inflation of 3.7% YoY and core PCE of 3.3% through June 2026 remain above the Fed's 2% target, while the labor market showed net job losses in July 2026, creating a contested policy environment.
5. Describe your hedging position. If you have interest rate swaps, caps, or other derivatives, explain how they limit or modify your exposure to a rate increase.

What to avoid: citing FedWatch as evidence that a hike "will" happen, or describing the probability as a Fed forecast. Both mischaracterize the tool and could draw SEC comment letter scrutiny.

ASC 820 Fair Value Measurement: When Does Repricing Require Action?

Under ASC 820, companies using discounted cash flow models or other market-based techniques must use inputs that reflect market participant assumptions as of the measurement date. When market-implied rate expectations shift by 20 or more percentage points in a single day, companies must assess whether their Level 2 or Level 3 fair value measurements remain appropriate.

The Jackson Hole repricing is exactly the kind of event that triggers this assessment. If your September 30, 2026 balance sheet carries interest-rate-sensitive instruments measured at fair value, the inputs used in those measurements should reflect the post-Jackson Hole rate environment, not the pre-speech baseline where a 70% hold probability prevailed.

For sensitivity disclosures, the richer distributional output from the Atlanta Fed Market Probability Tracker is more useful than FedWatch's single-probability figure. The Atlanta Fed tracker uses options on SOFR futures rather than Fed Funds futures, and it provides the full probability distribution plus the 25th-to-75th percentile range. That range can anchor your sensitivity analysis: rather than disclosing a single rate scenario, you can disclose the range of outcomes the market considers plausible.

For ASC 815 hedge accounting, the repricing also requires a hedge effectiveness reassessment. If you designated a cash flow hedge under ASC 815 when the rate environment looked materially different, the question is whether the hedge remains highly effective given the updated rate path implied by futures markets.

CME FedWatch vs. the Atlanta Fed Market Probability Tracker: Which to Cite?

Finance teams often default to CME FedWatch because it is the most visible tool. But for companies that need to document the basis for interest-rate assumptions in financial statements or disclosures, the Atlanta Fed Market Probability Tracker offers meaningful advantages.

The methodological difference matters for disclosure teams. SOFR is the replacement for LIBOR and the benchmark rate for USD-denominated securities. SOFR-based probabilities may diverge slightly from FedWatch's Fed Funds-based probabilities. Using both provides a more complete picture and a stronger documentation trail if your interest-rate assumptions are ever questioned in an SEC comment letter or audit.

The Atlanta Fed tracker's disclaimer is also worth noting: "CME Group market data are used, with permission from CME, as a source of information for this report. CME Group has no other connection to the Federal Reserve Bank of Atlanta's products and services."

Using FedWatch Probabilities in Earnings Calls: The PSLRA Safe Harbor Question

Companies can reference CME FedWatch probabilities in earnings calls and investor presentations, but the reference must be framed carefully to preserve the PSLRA safe harbor for forward-looking statements.

The Private Securities Litigation Reform Act protects companies that include meaningful cautionary language identifying important factors that could cause actual results to differ materially. When referencing FedWatch on an earnings call, the cautionary language should make three things clear:

1. The figure is a market-implied probability derived from futures pricing, not a Fed forecast or a certainty.
2. FedWatch probabilities can change materially with a single data release or speech, as demonstrated by the Jackson Hole repricing.
3. The actual FOMC decision may differ from market-implied expectations.

A safe harbor-compliant formulation might read: "As of [date], CME FedWatch, which derives probabilities from 30-Day Fed Funds futures, showed a market-implied probability of approximately 56% for a 25bp rate hike at the September 16 FOMC meeting. This figure reflects current futures market positioning and is not a Fed forecast. It can change materially with incoming economic data, and the actual FOMC decision may differ from market-implied expectations."

What to avoid: describing the probability as a "prediction" or citing it without cautionary language in a way that implies certainty about the rate path.

FAQ

What is the CME FedWatch September 2026 rate-hike probability right now? As of late September 2026, CME FedWatch showed approximately 56% probability of a 25bp rate hike at the September 16, 2026 FOMC meeting, up from a pre-Jackson Hole baseline where nearly 70% probability was assigned to no change. These figures are derived from 30-Day Fed Funds futures and change with each trading session.

Does a shift from 30% to 56% hike probability require an 8-K filing? A FedWatch probability shift alone does not trigger an 8-K obligation. The relevant question is whether the shift, combined with your company's specific interest-rate exposure, produces a material change in financial condition or results. Companies with very large floating-rate debt or significant interest-rate derivatives should document their materiality analysis explicitly.

How quickly can FedWatch probabilities change? Very quickly. The September 2026 repricing moved from roughly 30% to 56% hike probability following a single speech at Jackson Hole. A weak jobs report earlier in the cycle had moved probabilities by 20 or more percentage points in a single session. Disclosure teams should treat FedWatch as a real-time signal, not a stable assumption.

What is the Atlanta Fed Market Probability Tracker and how does it differ from FedWatch? The Atlanta Fed tracker uses options on SOFR futures rather than Fed Funds futures, and it outputs a full probability distribution with a 25th-to-75th percentile range rather than a single point probability. It is grounded in a peer-reviewed academic model and is updated daily. For financial statement assumptions and sensitivity disclosures, it provides a more defensible documentation trail than FedWatch alone.

Can we cite FedWatch in our 10-Q without triggering SEC scrutiny? Yes, provided you characterize it accurately as a market-implied probability from futures pricing, not a Fed forecast. Quantify your specific exposure to the rate scenario described, and pair the reference with meaningful cautionary language. A generic "interest rates may rise" sentence that ignores the specific September 2026 probability is more likely to draw SEC comment letter attention than a specific, well-framed disclosure.

What did Fed Chair Warsh actually say at Jackson Hole that moved markets? Warsh stated that better-than-expected summer inflation readings did not demonstrate that underlying trends had meaningfully improved, and that the Fed needed "confidence that underlying inflation was moving toward its objective clearly and quickly enough." That language, combined with three July FOMC dissenters and PCE inflation at 3.7% YoY, was enough to flip the market's base case from hold to hike.

The September 16 FOMC decision will settle the immediate question. What it will not settle is the disclosure obligation: companies that failed to reflect the genuine uncertainty in their Q3 filings will face that record regardless of what the Fed ultimately does.